The go-live checklist

Going live is the moment real orders start to flow, so it's worth a checklist. This lesson gives you one to work through for every new Integration, with the reason behind each item. Copy it into your own project notes and tick it off.

1. Product codes (SKU alignment)

For every product you plan to sync:

• Every SKU that will appear on inbound orders or data feeds exists in your ERP or inventory system's item master.
• SKU values match exactly across all connected systems, including letter case (Widget-A and widget-a are different), separators (hyphens or underscores) and leading zeros.
• There are no duplicate SKUs in either system.
• Each variant (a size or colour option) has its own unique SKU, in a format agreed across systems.
• Bundles and kits are accounted for: the bundle SKU exists as a single record in your item master, or you've agreed with your Supply Lens contact how component lines will be handled.
• Where a connected system uses different codes for the same product (for example a retailer's own codes), cross-references are in place in Supply Lens.

2. Master data

• Partner codes and barcodes are on your Products, scoped to the partner where needed.
• Conversions exist for every pack size partners order in, if you use Units of Measure.
• Parties exist for trading partners, with the identifiers their Documents carry and the codes your other systems need.
• Locations exist for warehouses and delivery points, with each system's code.
• Products have a default fulfilment Location.

3. The Integration

• The Integration is created and connected, with a clear name.
• Configurations exist for every document type in your build sheet, with the right direction.
• The matching Configurations exist on the Integrations at the other end of each flow.
• State is set if it's an EDI Integration; otherwise left unset.
• Default Unit of Measure is set only if the system always trades in one unit.
• For Shopify, webhooks are set up.

4. Mappings and running

• Every arrow in your build sheet has a Mapping: From, Map, As and To.
• Each Mapping is Enabled, and Automatic is on where you want it to run without anyone stepping in.
• Any filters (customer, Location, tags) are correct, or blank to apply to everything.
• A schedule is set, or you've agreed who will run the Integration manually and when.

5. Testing

• Tested end to end against a sandbox or in Test state, with manual Mappings, if possible.
• Test cases covered: a simple order, a multi-line order, a partner order using their codes, a pack size order, and the return journey (despatch and tracking).
• Every test Document has green ticks on its parties and lines, and its target data is Complete.
• Any test data has been cancelled or cleaned up in the target system.

6. Switching on

• Agree a go-live time when someone is around to watch, not late on a Friday.
• Switch Activation to Enabled. Some Integrations, such as Shopify, start their first sync straight away.
• Switch test Mappings to point at the live Integrations, and turn Automatic on.

7. The first week

• Check failed and Ready Documents at least twice a day.
• Spot-check a few Documents end to end each day: source data, Document, target data.
• Keep a log of every error and its fix; most will be master data gaps you can prevent next time.