Short answer
Data mapping defines how each piece of data in one system corresponds to data in another — which field goes where, how codes translate, and how structures differ. In ecommerce-ERP integrations it covers identifiers, customers, addresses, products, prices, taxes, shipping methods, and statuses. Good mappings are documented, kept in configuration where values change, validated on every record, and covered by automated tests.
Data mapping is the set of rules that translates data from one system’s model into another’s. Two systems almost never represent the same thing the same way: the store calls it a “variant,” the ERP calls it an “article”; the store says “paid,” the ERP needs a payment term code.
Three kinds of mapping
Field mapping
Which source field fills which target field. For example, the store’s shipping address zip becomes the ERP’s postal_code.
Value mapping
How codes and values translate. For example:
| Store value | ERP value |
|---|---|
| Shipping method “Express” | Carrier UPS, service EXP |
| Gateway “paypal” | Payment method PP |
| Location “Main warehouse” | Warehouse WH01 |
| Tax rate 20% | Tax code S20 |
Structural mapping
How shapes differ. A store order has one discount amount at order level; the ERP may require discounts per line. A product with variants in the store becomes several articles in the ERP. A bundle may become one line or many.
Areas that always need mapping in commerce
- Identifiers: order IDs, customer IDs, SKUs ↔ articles.
- Customers: guest vs. registered, B2B accounts, generic web customer.
- Addresses: field lengths, country and region codes, phone formats.
- Products: variants, units of measure, bundles, non-stock items.
- Money: currencies, tax-inclusive vs. exclusive prices, discount allocation, rounding.
- Shipping and payment methods.
- Statuses: order, payment, and fulfillment states.
Good practice
- Write a mapping specification listing every field, its source, transformation, and owner.
- Keep value tables in configuration, editable by authorized users.
- Validate every record: required fields present, codes mapped, totals matching after transformation.
- Fail loudly on unmapped values; never silently default.
- Make mapping functions pure (input → output, no side effects) so they are easy to unit test.
- Test with real data, including edge cases like long names, special characters, and unusual addresses.
- Version the mapping along with the code, and record which version processed each record.
Summary
Data mapping translates fields, values, and structures between systems. It is where most integration errors originate. Document it, keep changeable values in configuration, validate every record, fail on unmapped values, and test thoroughly. For a detailed example, see mapping products to ERP articles and SKUs.
Frequently asked questions
Who should own the mapping specification?
Business and technical people together. Business owners decide what values mean (which ERP payment term a gateway corresponds to); developers implement and validate the rules.
Should mappings be in code or configuration?
Structural rules belong in tested code. Value tables that business users change — shipping methods, payment gateways, warehouse codes — belong in configuration, so updates do not require a deployment.
What should happen when a value has no mapping?
Fail the record into a review queue with a clear message. Silent defaults hide problems until they show up in financial reports.
Sources and further reading
Platform-specific statements on this page were checked against these sources on . Vendor APIs change; confirm details in the current documentation before you build.
- [1] Shopify Order object — Shopify
- [2] Enterprise Integration Patterns — message translator — Gregor Hohpe and Bobby Woolf
Related reading
- Guides How to Map Ecommerce Products to ERP Articles and SKUs Design product and variant mapping between an ecommerce platform and an ERP — SKU strategy, variants, bundles, units of measure, cross-references, and validation.
- Guides How to Synchronize Shopify Orders with an ERP How to export Shopify orders to an ERP reliably — choosing the trigger, mapping lines, taxes, discounts and payments, handling edits, and avoiding duplicates.
- Concepts What Is Ecommerce ERP Integration? What ecommerce ERP integration means, which workflows it automates, how data flows between store and ERP, and the main approaches used to build it.
- Guides How to Handle Refunds and Cancellations in an ERP Integration Model ecommerce refunds, cancellations, and returns in an ERP — credit notes, restocking, partial refunds, shipping refunds, and which system initiates each action.