Warehouse scanner connected to an inventory reconciliation checklist for ShipHero and Acumatica

ShipHero and Acumatica inventory reconciliation means comparing warehouse activity with the ERP transactions that should represent it, then resolving each difference before it becomes a customer promise or accounting problem. A useful process starts with shared item and warehouse identifiers, a clear definition of each quantity, a transaction cutoff, and an exception queue. It does not assume that a successful integration message proves the two systems agree. This guide explains the controls a distributor should design around orders, picks, shipments, returns, adjustments, and physical counts, with a daily review that finance and warehouse teams can actually operate.

Why fulfillment reconciliation deserves its own workflow

Back to contents

An order can be picked in the warehouse while the ERP still shows stock available. A shipment can be acknowledged by one system while its corresponding inventory transaction waits for a later posting step. A return can be received physically but remain unavailable for resale. These differences are often legitimate for a short period. The control problem begins when no one can tell which differences are expected, which are late, and which require correction.

Biz-Tech Services describes its ShipHero and Acumatica integration as a way to connect warehouse and ERP workflows. The integration design and configuration determine the actual objects, direction, and timing for a particular customer. The reconciliation method below is therefore an operating framework to validate against the deployed connector, rather than a claim that every transaction moves automatically in every installation.

Define the system of record for each decision

Back to contents

Before reconciling numbers, decide which system owns each business event. A warehouse management system normally records operational fulfillment steps; an ERP records commercial and financial transactions. The exact handoff should be documented per event: order release, pick completion, shipment confirmation, inventory adjustment, return receipt, and period close. If both systems can change the same field, define the conflict rule and audit trail.

The key question is not simply “Which inventory number is right?” It is “Which event happened, when did it become final, and which system has recorded it?” That framing makes a difference actionable.

Build an inventory quantity dictionary

Back to contents

“Inventory” can mean physical units on a shelf, units available to allocate, units already allocated to orders, units in transit, or the ERP balance after posted transactions. These should not be compared as if they were identical. ShipHero’s inventory update webhook documentation describes an available quantity derived from on hand, allocated, sell ahead, and reserve fields. That formula is a product-specific definition, not an instruction to compare it directly with every Acumatica availability field.

Document the precise field, unit of measure, location scope, lot or serial scope, and timing for each comparison. Start with like-for-like on-hand quantities where feasible. For availability, document reservation and allocation rules separately. A five-unit variance can disappear once the team finds that one report includes allocated stock and the other does not.

Map item, warehouse, and location identifiers

Back to contents

Each comparison row needs a reliable key. Confirm the ShipHero product or SKU identifier, Acumatica inventory ID, warehouse, location, unit of measure, and any lot or serial number that matters. The mapping should be unique for the scope being reconciled. A duplicate SKU, inactive item, renamed warehouse, or case-versus-each conversion can create an apparent stock variance even when transactions moved correctly.

Biz-Tech’s SKU mapping lesson offers related context. Treat your actual integration mapping as the authority; do not assume a universal one-to-one field rule from a general article. Store mapping changes with an effective date so past transactions can still be explained.

Establish a shared cutoff before comparing balances

Back to contents

Choose a comparison time and record both systems’ timestamps and time zones. Export the ERP balance and warehouse balance as close to the same cutoff as practical. Then separate transactions completed before the cutoff from those that occurred afterward. A report run at 17:00 in one system and 17:10 in another can differ simply because orders shipped in the ten-minute gap.

For a daily process, publish a cutoff rule such as “completed shipments through 16:30 local warehouse time, with a 30-minute processing allowance.” The allowance is a proposed operating control, not a documented ShipHero or Acumatica service guarantee. Set it from observed integration behavior and revise it when the workflow changes.

Reconcile shipments from event to ERP posting

Back to contents

For each warehouse-confirmed shipment, match order number, shipment identifier, item, quantity, warehouse, and completion time to the corresponding Acumatica shipment or inventory transaction. Check status at both the warehouse and ERP layers. An integration can transmit a shipment event while the ERP document still requires validation or release.

Classify unmatched shipments by age. A newly completed shipment may be within the normal processing window. An older unmatched shipment needs an owner and a reason: failed mapping, rejected ERP document, partial shipment, duplicate event, or a missing transaction. Never “fix” the balance with an adjustment until the missing event is understood; otherwise the eventual posting can create a second variance.

Treat partial shipments and cancellations separately

Back to contents

An order line for ten units may be fulfilled in two shipments of six and four. Comparing the order quantity with a single shipment will produce a false exception. Reconcile at the shipment-line level, then roll up to the order. For cancellations, identify whether the warehouse released an allocation and whether the ERP also reversed its commitment. These are distinct state changes.

The Biz-Tech order synchronization lesson is useful background on the order flow. The reconciliation control should still check the exact statuses and identifiers in the customer’s deployment.

Reconcile receipts, transfers, and returns by disposition

Back to contents

Inbound units should be compared by receipt or transfer reference, item, quantity, warehouse, and posting status. A warehouse receipt does not necessarily mean every unit is available for sale. Returns may be pending inspection, damaged, quarantined, or restocked. Preserve those dispositions so operations do not mistake physically present units for sellable stock.

For transfers, compare the ship-out and receive-in legs rather than netting them prematurely. In-transit stock is a timing state, not automatically a lost unit. Escalate aged in-transit lines separately from true quantity differences.

Use an exception queue instead of a single variance number

Back to contents

A useful queue contains the item key, warehouse, quantity definition, both observed balances, difference, event reference, latest status, age, likely cause, owner, and next action. Group exceptions into mapping, timing, missing transaction, rejected transaction, allocation rule, physical count, and unresolved categories. This turns a report into a worklist.

Set thresholds by risk rather than one blanket tolerance. A one-unit difference on a serialized or high-value item may require immediate review; a temporary timing difference on a fast-moving item may be expected. Thresholds should never hide accumulating exceptions.

Distinguish webhook delivery from transaction completion

Back to contents

ShipHero documents webhooks as asynchronous notifications. A webhook arriving at an endpoint does not by itself prove that Acumatica accepted, posted, or released the corresponding document. Capture a traceable event or correlation ID, the connector result, and the ERP document status. The inventory change webhook can describe a quantity delta and its reason or source, but the downstream business outcome still needs validation.

Design retries to be idempotent: processing the same event again should not create a second shipment or adjustment. Verify this in the actual connector and test environment rather than assuming it. Keep failed events visible until a person or a monitored recovery process resolves them.

Investigate a variance in a fixed order

Back to contents

First, confirm that both numbers use the same item, warehouse, unit, and cutoff. Second, inspect recent shipments, receipts, transfers, returns, and adjustments around the difference. Third, check integration logs and ERP document errors. Fourth, verify allocation or reserve rules. Finally, request a physical count if the transaction trail cannot explain the balance. This order avoids using a count or manual adjustment to mask a process issue.

Record the root cause and correction separately. “Reprocessed shipment 123” is a correction; “ERP document rejected because item mapping was inactive” is the cause. The distinction helps prevent recurrence.

Run a daily reconciliation cadence

Back to contents

At the agreed cutoff, capture balance snapshots and transaction extracts. Normalize keys and quantities, match completed events, and issue the exception queue. Assign warehouse operations the physical/event questions, integration support the transmission and mapping questions, and ERP finance or inventory control the posting and adjustment questions. Review aged exceptions before the next customer promise or purchasing cycle.

The cadence should end with a signed-off status: matched items, explained timing differences, open exceptions, and corrections completed. A dashboard without ownership is only a display. A short daily review is more valuable when it consistently closes or escalates the same categories.

Integrate physical inventory counts without losing the audit trail

Back to contents

Acumatica’s physical inventory guidance describes preparation steps before counting and its completion guidance covers count completion. Use that formal process when a physical count is required. Freeze or carefully track movements during the count window according to the chosen method, then reconcile count differences to both warehouse and ERP records.

Do not treat a count adjustment as the whole answer. Preserve the pre-count balance, counted quantity, adjustment document, approver, and suspected cause. If the same SKU repeatedly needs adjustment, examine scanning, returns disposition, unit conversion, or integration mapping.

Test the workflow with controlled scenarios

Back to contents

Before relying on automated reconciliation, test a normal full shipment, partial shipment, canceled order, return in quarantine, warehouse transfer, item mapping change, and a deliberately rejected ERP transaction. For each, write the expected state in ShipHero, the connector, and Acumatica. Check the exception queue and recovery path. Run tests across a cutoff and time-zone boundary because those are common sources of false variances.

Use production-like item and warehouse structures but avoid exposing customer data in test reports. Retain test evidence and update the runbook after configuration changes. The objective is to prove that staff can identify and resolve a mismatch, not just that a happy-path transaction succeeded once.

Measure control quality, not just message volume

Back to contents

Track the number and age of open exceptions, unmatched shipments, repeat mapping errors, manual adjustments, and time from warehouse completion to ERP posting. Review trends by warehouse and item category. A high volume of “successful” integration events can coexist with aged inventory differences, so message count alone is a weak measure.

Set baselines from your own operation. Do not promise a universal reconciliation rate or processing latency. If a metric deteriorates after a connector or ERP change, use transaction-level evidence to identify the specific step that changed.

A practical implementation sequence

Back to contents

Start by documenting the deployed data flow and quantity definitions. Next, clean item and warehouse mappings. Then establish the cutoff, exports, and transaction matching rules. Build a small exception queue and assign owners before adding alerts or automation. Test the controlled scenarios, run parallel daily reviews, and only then make the process routine. This sequence keeps the control understandable and repairable.

Biz-Tech Services can help evaluate the ShipHero integration and its Acumatica marketplace context against your actual warehouse and ERP process. The useful starting artifact is a transaction map and sample variance list, not a promise that two summary balances will always match instantly.

Frequently asked questions

Back to contents

What should I compare first between ShipHero and Acumatica?

Begin with a mapped item and warehouse, a shared cutoff, and a clearly defined on-hand quantity. Then compare the transactions that explain any difference. Do not compare an available-to-sell field with an ERP on-hand field without accounting for allocation and reserve rules.

Does a successful webhook mean the ERP inventory is updated?

No. A webhook can indicate that a notification was emitted or received. The connector and Acumatica document still need to accept and complete the relevant transaction. Verify the final document status.

How should partial shipments be reconciled?

Match each shipment line to its ERP counterpart, then roll the lines up to the order. Keep shipped, unshipped, and canceled quantities separate.

Why do balances differ at the end of the day?

Common causes include different cutoff times, pending ERP posting, unmatched shipments, mapping errors, allocation definitions, returns disposition, and physical stock differences. The exception queue should distinguish these causes rather than group them into one number.

Should we post an inventory adjustment whenever the balances differ?

Only after identifying the cause and confirming an adjustment is the correct transaction. A pending shipment or failed document may later post and double the correction.

How do returns affect available inventory?

A returned unit can be physically present but not sellable while it awaits inspection or disposition. Reconcile the return receipt and its final stock status separately.

How often should the team reconcile?

Daily is a practical starting cadence for active fulfillment operations, with faster alerts for high-risk exceptions. Choose the interval from order volume, operational risk, and measured processing times.

What evidence should be kept for an exception?

Keep both balance snapshots, timestamps, transaction references, integration result, ERP document status, owner, correction, and root cause. This record supports review and makes repeated problems visible.

What is the first step if we are implementing a connector?

Write down which system owns each event and define the exact item, warehouse, quantity, and status mappings. Then test normal and failure scenarios before using a dashboard as the control.

Conclusion

Back to contents

ShipHero and Acumatica inventory reconciliation works when every variance has a defined quantity, a shared cutoff, a traceable event, and an owner. Build the process around shipment and receipt evidence, distinguish temporary timing from real errors, and reserve manual adjustments for verified differences. A small daily exception queue gives operations, IT, and finance a common way to close the gap.

Sources

Back to contents

Privacy Preference Center