{"id":999,"date":"2026-09-22T09:08:52","date_gmt":"2026-09-22T09:08:52","guid":{"rendered":"https:\/\/smppcenter.com\/kb\/?p=999"},"modified":"2026-09-22T09:08:54","modified_gmt":"2026-09-22T09:08:54","slug":"map-vendor-error-codes-global-error-codes","status":"publish","type":"post","link":"https:\/\/smppcenter.com\/kb\/map-vendor-error-codes-global-error-codes\/","title":{"rendered":"How to Map Vendor Error Codes to Global Error Codes (Including Bulk CSV Import)"},"content":{"rendered":"\n

Vendor error code mapping connects a vendor’s raw codes to your Global Error Codes<\/strong>. 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<\/strong>, which clients can’t act on.<\/p>\n\n\n\n

Where to find it<\/h3>\n\n\n\n

Sidebar \u2192 Settings\u2192 Error Codes<\/strong>, then the Manage Vendor Error Codes<\/strong> screen.<\/p>\n\n\n\n

Add a single mapping<\/h3>\n\n\n\n
    \n
  1. Click Add<\/strong>.<\/li>\n\n\n\n
  2. Product:<\/strong> SMS, WhatsApp, etc.<\/li>\n\n\n\n
  3. Global Error Code:<\/strong> the code your client will see.<\/li>\n\n\n\n
  4. Vendor:<\/strong> the vendor this code comes from.<\/li>\n\n\n\n
  5. Vendor Error Code:<\/strong> the exact code the vendor returns.<\/li>\n\n\n\n
  6. Vendor Error Description:<\/strong> what the vendor says it means. Keep this for your own team.<\/li>\n\n\n\n
  7. Click Save Changes<\/strong>.<\/li>\n<\/ol>\n\n\n\n

    To map a similar code quickly, use Clone<\/strong> on an existing row.<\/p>\n\n\n\n

    Bulk import (for onboarding a new vendor)<\/h3>\n\n\n\n
      \n
    1. In Import Vendor Error Codes<\/strong>, click Select File<\/strong>.<\/li>\n\n\n\n
    2. Upload .xls<\/code>, .xlsx<\/code> or .csv<\/code>. Download the sample file<\/strong> first and match its columns.<\/li>\n\n\n\n
    3. Click Save Changes<\/strong>.<\/li>\n<\/ol>\n\n\n\n

      You can upload up to 50,000 rows<\/strong> per file.<\/p>\n\n\n\n

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

        Troubleshooting<\/h3>\n\n\n\n