Requesting a mapping change

How to raise a mapping change request with HighCohesion and what to expect.

Mapping changes

Mapping changes are modifications to your integration's transformation logic — things like ERP field mappings, product categorisation, tax codes, filter conditions, or how discounts are represented. These cannot be made from the Control Panel; they require HighCohesion to update the underlying stream configuration.

Why mapping changes go through HC

The mapping logic for each stream lives in a transformation — a structured file defining how every field translates between your systems. Transformations are either public (shared, standard mappings used across customers, editable only by HC once live) or private (specific to your organisation). Either way, a change is made against tested, versioned logic rather than edited ad hoc — which is why changes follow the request-and-UAT process below instead of being edited directly in the Control Panel.

What counts as a mapping change

  • Changing which ERP field a Shopify value maps to

  • Updating product categorisation or classification logic

  • Adjusting tax code assignments

  • Modifying filter conditions (e.g. which orders get synced)

  • Changing how discounts, promotions, or bundles are represented in your ERP

How to raise a request

Contact your HighCohesion account team with the following:

  • Stream name — the specific integration stream affected

  • Current behaviour — what is happening now

  • Desired behaviour — what you need it to do instead

  • Sample reference — an order number, event ID, or payload example that illustrates the issue

  • Deadline — if the change is time-sensitive, flag this upfront

The more specific you are, the faster HC can scope and deliver the change.

What happens next

  1. HC confirms the scope of the change and any downstream implications

  2. The change is made in your test environment

  3. HC tests against your sample data and validates the output

  4. You complete UAT in the test environment

  5. HC deploys to production once UAT is signed off

Allow reasonable lead time for UAT, especially if the change affects live order flows.