Skip to main content
Making a change

Going live with a new platform

How to add a new system to your HighCohesion integration — what to prepare, and what to expect.

When to use this

Use this guide when you want to add a new platform to your integration: a new ERP, storefront, 3PL or payment provider. Adding a platform is a project, not a self-service change, so HC scopes, builds and launches it with you. For the systems HC connects, see Systems HighCohesion connects; for how streams fit together, see How your integrations are structured.

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

Before you start

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

  • The name of the system you want to connect

  • Which data flows you need (for example orders from Shopify to NetSuite, or 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

  • How to reach HC: see How to get support

Steps

Raise the request

  1. Contact HC with the information listed above.

Work through the delivery process

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

  1. Review and sign off the solution design. HC produces a solution design document covering the proposed stream architecture, field mappings, transformation logic, and any known risks or dependencies. Build does not begin until you have signed off.

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

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

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

Monitor after go-live

  1. Monitor the Control Panel closely in the days following go-live, specifically the event list and any active alerts.

  2. Flag anything unexpected to HC promptly. Early issues are much easier to resolve than ones discovered days later.

What you should see

After cutover, the new streams are enabled in production and their events appear in the Control Panel event list. For what a normal event list and dashboard look like, see What a healthy integration looks like and Understanding event statuses.

If it did not work

Something unexpected appears in the event list or alerts after go-live. Flag it to HC promptly rather than waiting; early issues are much easier to resolve than ones discovered days later. If an alert fired, see I received an alert — what now?.

You cannot avoid launching during a high-volume trading event. Discuss the risk with HC in advance so additional monitoring can be arranged.

To contact HC, see How to get support.

Related

Was this helpful?

Still need help? Ask the team