The Scenario
You are a fulfillment coordinator at an e-commerce warehouse. The daily dispatch batch runs at 6 AM. You have a Google Sheet with 200 customer orders, each with a city KLADR code in column A pulled from the order management system.
Your warehouse software needs the CDEK, Boxberry, and DPD city IDs to route each order to the right carrier API. Without those IDs, the warehouse system cannot select the endpoint, and orders sit in a manual queue until someone looks them up by hand.
The bad version of yesterday:
- Open the CDEK partner portal
- Search each KLADR code manually to find the city ID
- Copy it to the sheet
- Open the Boxberry portal, repeat
- Open the DPD portal, repeat
- Do this for 200 rows across three 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 spreadsheet 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 my sheet, 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 that row's columns B, C, and D.
SheetXAI reads column A, calls DaData's delivery ID resolver for each row, and writes three columns of carrier IDs 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 explicit. If a KLADR code resolves to a location that none of the three carriers serve, you see it in the sheet before the batch runs — not as an API error 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, depending on which intake form the customer used.
For each value in column A, detect whether it is a KLADR code (numeric) or a FIAS GUID (hyphenated). Use the appropriate DaData lookup for each format and write the CDEK, Boxberry, and DPD IDs into columns B, C, and D.
When you only want CDEK IDs because CDEK is your primary carrier
The Boxberry and DPD columns slow down the batch setup this week. You only need CDEK.
For each KLADR code in column A, 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 sheet has a mix of this week's new orders and last week's orders that were already mapped.
Skip any row where column B already contains a value. For all rows where column B is empty, run the DaData delivery ID lookup using the KLADR code in column A 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 team
The operations manager wants to know which cities are not covered by any of the three carriers before the dispatch window.
For each KLADR code in column A, use DaData to fetch CDEK, Boxberry, and DPD city IDs into columns B, C, and D. Then write a summary below the data: 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. The ops manager gets the report alongside the dispatch file.
Try It
Get the 7-day free trial of SheetXAI and open any sheet 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 or the DaData in Google Sheets overview.