Publish Date :
Connecting POS, ERP and Ecommerce to One Plan
POS, ERP and ecommerce data become useful to one plan when the retailer agrees what each system owns and how repeated or delayed records are reconciled. Core holds the merchandise assumptions; configured integrations provide the operational inputs and supported writes. A list of connected systems is only the start.

THE MERCHMIX DECISION / Core
A connection needs a shared stock definition
Planning integrations need agreed owners, timestamps and transaction meanings, so the same sale is not counted twice and future stock is not treated as usable today.
Independent retail planning example. Financial amounts are US dollars. Forecasts, quantities and proposals are assumptions for this decision, not customer results.
Canvas bags / snapshot and event reconciliation
| Record owner | Meaning |
|---|---|
| POS | Completed store trading |
| ERP | Accepted inventory and receipt basis |
| Ecommerce | Orders and active reservations |
All clocks in this independent example use one agreed timezone.
The accepted physical snapshot contains 240 canvas bags at 09:00.
THE KEY IDEA
Agree the owners and event boundaries first, then give Core a reconciled current position and a separately defined forward commitment.
Define the measure before connecting another source
The POS may own completed store sales, the ERP an accepted inventory basis and ecommerce the current order reservations. Those roles depend on the retailer’s architecture. Connecting the files without defining the measures can replace a spreadsheet disagreement with a faster automated disagreement.
Merchmix describes connections to retained operating systems. Actual mappings, refresh cadence and write permissions need deployment-specific validation. Core’s planning role should remain clear: it compares commercial assumptions using the accepted inputs rather than making every source record authoritative at the same time.
Use a snapshot boundary the team can explain
The independent example begins with 240 physical canvas bags at 09:00. The next reconciliation is at 09:10, with both times in one agreed timezone. Identify which transactions are already included in the opening snapshot before applying any later movement.
An ERP stock file taken at 09:10 may already include a sale delivered separately by the POS feed. Subtracting that sale again would understate inventory. Give the integration a clear watermark or equivalent reconciliation rule, with an owner for exceptions, rather than assume every incoming message represents new stock movement.
Reconcile accepted movements once
After the chosen 09:00 boundary, twelve units sell and two returned units are accepted as saleable. Physical stock becomes 230: 240 less twelve plus two. The net movement is ten units. This is an operational example, not a claim about any particular retailer’s connector implementation.
Shopify’s delivery guidance explicitly allows for repeated webhook delivery. Receiving the same underlying business event again must not create another movement. The appropriate event identity and retry handling depend on the source and API contract; a generic planning article should not prescribe one identifier for every integration.
THE FIGURES BEHIND THE DECISION
| Control | Evidence |
|---|---|
| Freshness | 09:10 reconciliation boundary |
| Replay | Twelve sales not subtracted again |
| Write-back | Supported action and authority only |
Physical reconciliation: 240 less 12 sales plus 2 saleable returns = 230. Usable current basis: 230 less 18 reserved = 212. Forty incoming units remain separate.
Keep reservation and arrival states separate
At 09:10, eighteen active reserved units sit within the 230 physical units. Excluding those reservations once gives 212 usable units under this example’s definition. Forty units expected later remain a separate incoming record. They are not added to today’s available balance.
Real source systems may already supply an availability value after their restrictions. Confirm that basis before subtracting reservations again. Core needs a reconciled opening position and the relevant future commitment, with exceptions visible where the connection cannot establish a dependable current value.
Make configured write-back as specific as the read
A plan change, a supplier order, a stock movement and a price update are different actions. Confirm which system accepts each one and what authority applies before enabling a supported write. Reading an inventory balance is not evidence that all transactional updates are configured.
Use the Core comparison to make the proposed commercial change visible, then verify the supported downstream outcome. The retailer should be able to distinguish a saved planning assumption, an authorised instruction and a confirmed operating-system response. None should be inferred solely from a connector status label.
Test delay, replay and incomplete data before relying on the plan
Reproduce a delayed source update and a repeated event in the agreed test scope. Check which value the team will see, how the exception is surfaced and who resolves it. A connection that works only when every message arrives promptly has not answered the operating question.
The example’s accepted current basis remains 212 and its future incoming quantity forty. If the source snapshot is stale or the reservations cannot be reconciled, qualify the result instead of presenting the same precise number as dependable. Core’s decision quality depends on that input discipline.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Source snapshot | Core / evidence | The accepted physical snapshot contains 240 canvas bags at 09:00. |
| Post-snapshot movement | Core / comparison | Twelve sales and two saleable returns after the snapshot give 230 physical units. |
| Core hand-off | Core / decision review | Refresh cadence, error handling and permitted writes must be validated for the deployment. |
Run the integration as an owned trading process
Retain the field meanings, scope, timestamps and exception owners alongside the configured connection. Recheck them when the retailer adds a channel or changes a source system. A technically successful transfer of data can still change the meaning of a planning measure.
Merchmix Core connects the plan with the systems the retailer keeps. The practical benefit comes from a repeatable, understood operational basis and controlled next actions, rather than a promise that one connection removes every timing, ownership or reconciliation decision.
BEFORE THE NEXT DECISION
- Planning owner
The integration needs event matching and reconciliation appropriate to its source.
- Commercial owner
The reservation and source definitions must be agreed for the connected system.
- Decision owner
Refresh cadence, error handling and permitted writes must be validated for the deployment.
Common questions
Should the POS and ERP sales feeds both reduce stock?
Only according to the agreed source and snapshot boundary. The same business movement must not be applied twice.
Why does physical stock become 230?
240 opening units less twelve sales plus two accepted saleable returns equals 230.
Why are only 212 units usable?
Eighteen reserved units are included in the 230 physical units and are excluded once under the example’s definition.
Can the forty incoming units be promised as current stock?
Not on this current-stock basis. They retain a future arrival and commitment state.
Does every integration support the same writes?
No. Source mappings, refresh cadence, authority and supported write-back actions need validation for the actual deployment.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.