The Scenario
You are a fulfillment coordinator at an e-commerce warehouse. The daily dispatch batch runs at 6 AM. You have an Excel workbook with 200 customer orders on the Orders tab, each with a city KLADR code in column A from the order management system.
Your warehouse software needs CDEK, Boxberry, and DPD city IDs to route each order to the right carrier API. Without those IDs, orders sit in a manual queue.
The bad version of yesterday:
- Open the CDEK partner portal
- Search each KLADR code manually
- Copy the city ID to the workbook
- Repeat for Boxberry and DPD portals
- Finish at 7:15 AM, 75 minutes after the batch was supposed to run.
The fast version is one prompt before the shift starts.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Excel workbook that reads the KLADR column, calls DaData's delivery service ID lookup for every row, and writes the carrier IDs back into three columns.
Open the SheetXAI sidebar and type:
For each KLADR code in column A of the Orders tab, use DaData to fetch the CDEK city ID, the Boxberry city ID, and the DPD city ID. Write the CDEK ID into column B, the Boxberry ID into column C, and the DPD ID into column D. If DaData returns no result for a code, write "NOT FOUND" in columns B, C, and D for that row.
SheetXAI reads column A of the Orders tab, calls DaData for each row, and writes three carrier ID columns back. All 200 orders mapped before the 6 AM dispatch window.
What You Get
Three enriched carrier ID columns next to every order:
- Column B — CDEK city ID for the carrier API
- Column C — Boxberry city ID
- Column D — DPD city ID
NOT FOUND rows are visible before the batch runs, not as API errors at 6:02 AM.
What If the Data Is Not Quite Ready
Order system exports have inconsistencies. SheetXAI handles them in the same prompt.
When KLADR codes are mixed with FIAS codes in the same column
Your order system exports KLADR codes for some cities and FIAS GUIDs for others.
For each value in column A of the Orders tab, detect whether it is a KLADR code (numeric) or a FIAS GUID (hyphenated). Use the appropriate DaData lookup for each format and write CDEK, Boxberry, and DPD IDs into columns B, C, and D.
When you only want CDEK IDs this week
The Boxberry and DPD columns can wait. You only need CDEK for Monday's batch.
For each KLADR code in column A of the Orders tab, use DaData to fetch only the CDEK city ID and write it into column B. Leave columns C and D blank.
When some orders already have a carrier ID from a previous run
The workbook has a mix of new orders and last week's already-mapped orders.
Skip any row in the Orders tab where column B already contains a value. For all rows where column B is empty, run the DaData delivery ID lookup and write CDEK, Boxberry, and DPD IDs into columns B, C, and D.
When you need the carrier IDs plus a coverage report for the ops manager
The ops manager wants to see which cities are not covered by any carrier before the dispatch window.
For each KLADR code in column A of the Orders tab, fetch CDEK, Boxberry, and DPD city IDs into columns B, C, and D. Then create a new sheet called "Coverage Report": total orders, number with at least one carrier ID found, number where all three returned NOT FOUND, and the top five KLADR codes with missing carrier coverage.
The pattern: the ID mapping and the coverage analysis come from the same prompt.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook with Russian city KLADR or FIAS codes, then ask it to map them to delivery service IDs using DaData. The DaData integration is included in every SheetXAI plan. For related workflows, see how to standardize and geocode Russian addresses in Excel or the DaData in Excel overview.