How to Map Vendor Error Codes to Global Error Codes (Including Bulk CSV Import)

Vendor error code mapping connects a vendor’s raw codes to your Global Error Codes. When a DLR comes back from a vendor, the platform looks up that vendor’s code, finds the global code it’s mapped to, and sends the global code to your client. Any code without a mapping reaches the client as the default code or UNDEFINED, which clients can’t act on.

Where to find it

Sidebar → Settings→ Error Codes, then the Manage Vendor Error Codes screen.

Add a single mapping

  1. Click Add.
  2. Product: SMS, WhatsApp, etc.
  3. Global Error Code: the code your client will see.
  4. Vendor: the vendor this code comes from.
  5. Vendor Error Code: the exact code the vendor returns.
  6. Vendor Error Description: what the vendor says it means. Keep this for your own team.
  7. Click Save Changes.

To map a similar code quickly, use Clone on an existing row.

Bulk import (for onboarding a new vendor)

  1. In Import Vendor Error Codes, click Select File.
  2. Upload .xls, .xlsx or .csv. Download the sample file first and match its columns.
  3. Click Save Changes.

You can upload up to 50,000 rows per file.

Checklist for onboarding a new vendor

  1. Get the vendor’s full error code list in writing, including their DLR err: values.
  2. Build the mapping sheet against your existing global catalog. Only add new global codes when a vendor code really needs different client action.
  3. Import the sheet, then run test traffic that triggers common failures (invalid number, absent subscriber).
  4. In Message Log, filter by the new connect and check that no rows show UNDEFINED.
  5. Before connecting the new route, export the vendor mapping list and keep it with your vendor contract.

Troubleshooting

  • Client sees UNDEFINED: the vendor returned a code you haven’t mapped. Find the raw code in the message details and add a mapping.
  • CSV rejected: re-save it from the sample file template and check column order. On recent versions, file-type detection issues on CSV uploads are fixed, so update if you’re running an older build.
  • Same vendor code, different meaning per product: map it once per product, since Product is part of the mapping.

Related articles

Found this useful?Add as Preferred Source on Google
Tagged: