Going live with a new platform

Adding a new platform to your integration (a new ERP, storefront, 3PL, or payment provider) is a project, not a self-service change. This article explains what's involved and how to get started.

Before you raise a request

Gather the following before contacting HC:

• The name of the system you want to connect

• Which data flows you need (e.g. orders from Shopify to NetSuite, inventory from NetSuite to Shopify)

• Any known constraints (legacy field mappings, unusual data formats, shared SKUs across stores)

• Your target go-live date or window

The more context you provide upfront, the faster HC can size and scope the work.

What happens next

Once you raise a request, HC follows a structured delivery process:

1. Solution design HC produces a solution design document covering the proposed stream architecture, field mappings, transformation logic, and any known risks or dependencies. You review and sign off before build begins.

2. Build HC configures and builds the streams in a non-production environment. This includes writing transformation logic, setting up error handling, and connecting to your systems.

3. UAT (User Acceptance Testing) You test the integration end-to-end against real or representative data. HC supports you through this phase, triaging any issues and making adjustments.

4. Cutover HC coordinates the go-live, which typically involves enabling streams in production and monitoring closely for the first hours of live traffic.

After go-live

Monitor the Control Panel closely in the days following go-live — specifically the event list and any active alerts. Flag anything unexpected to HC promptly; early issues are much easier to resolve than ones discovered days later.

Timing

Avoid launching a new platform at the same time as a high-volume trading event (sale, product launch, peak season). If timing is unavoidable, discuss the risk with HC in advance so additional monitoring can be arranged.