SKU Naming Convention
Start here. This page explains the SKU code that drives the schema, gateway selection, and the capability bitmap. Read this before you open any gateway or product-page detail.
Partially generated. The structural rules are deterministic. Variant letter meanings (section below) must be authored by TW.
Format
INDUSTRY - REGION - SOLUTION - VARIANT - CAPABILITIES
C2C - US - 1003 - B - 010010
| | | | |
| | | | +-- 6-bit capability bitmap
| | | +------------- Variant letter
| | +------------------------ Solution ID (gateway + integration)
| +--------------------------------- Region code
+------------------------------------------- Industry code
Segment Reference
| Segment | Position | Reference |
|---|---|---|
| Industry | 1st | Industry Codes |
| Region | 2nd | See region codes below |
| Solution | 3rd | Solution IDs |
| Variant | 4th | See variant types below |
| Capabilities | 5th | Payment Method IDs |
Region Codes
These are the region codes currently represented in the repo and in the sample SKUs. ALL is used when the same solution is intended to be global rather than region-specific.
| Code | Region | Notes |
|---|---|---|
US |
United States | Used for US-specific product variants |
EU |
Europe | Used for Europe-specific product variants |
ALL |
All regions (global) | Used when no region-specific config exists |
Variants
Variant letters distinguish implementation variants for the same solution family. In this repo, the letter is part of the SKU and should be read together with the solution ID, but the exact business meaning of each letter should be confirmed with the owning integration team before publishing.
|