Production go-live checklist#

Use this checklist before the first real customer orders are processed through StackCube. The goal is not to finish every possible setup task. The goal is to make the first channel safe enough for daily operation.

Data readiness#

Confirm the first production channel has enough reference data:

• Active items include SKU, item name, unit, status, and default price.
• High-volume items have aliases for the names customers actually use.
• Inactive or discontinued items are not exposed for new portal orders.
• Priority customers have customer code, contact, internal assignee, and ERP or internal customer code.
• Customer price tiers or tier rules exist for accounts where price mistakes create shipment or invoice risk.

Channel readiness#

Start with one channel unless the team already handles the same workflow reliably in the sample environment.

• Email forwarding or upload has been tested with real examples.
• The team knows where to find original messages, attachments, and intake history.
• Unknown sender behavior is documented.
• Duplicate-looking orders are held for review instead of approved immediately.
• Customer-facing portal links are shared only with customers whose catalog and prices are ready.

Review policy#

Before go-live, write down who can make each decision:

• Who checks customer and item matches.
• Who can approve a corrected order.
• Which exceptions must be rejected instead of edited.
• Which order value or customer type needs a second approval.
• Who updates catalog aliases, customer price tiers, and tier rules after repeated corrections.

Export handoff#

Run at least one sample handoff before live approval:

• Carrier CSV opens with the expected columns and encoding.
• Sender name, phone, and address are correct.
• ERP or accounting codes match the customer and item records.
• Manual export steps are written down if supported ERP export is not live.
• Re-export rules are clear so duplicate shipments are avoided.

First week routine#

During the first week, review setup data every day. Look for repeated unmatched items, price overrides, duplicate warnings, and rejected orders. Add aliases and pricing rules only after the correction pattern is clear.

Do not add a second channel until the first channel can be reviewed, approved, and exported without private side conversations.