Warehouse shipping desk with label printer, parcel tracking screens, and connected Acumatica order data

A ShipStation–Acumatica order should close only when its expected quantities, actual shipments, package tracking, carrier details, and billing handoff agree. A printed label alone does not prove the carrier received a parcel, and one tracked parcel does not prove a split order is complete. Teams need to choose the integration direction, map stores, warehouses and shipping methods, and test each state change before automating closeout. This guide focuses on the practical evidence needed to move an order from fulfillment to invoice without losing an open quantity, a second package, or a customer notification. It distinguishes the Biz-Tech Services ShipStation Connector from ShipStation’s separately documented Acumatica store integration, because configuration and limitations can differ.

Table of Contents

  1. Which ShipStation–Acumatica integration is in scope?
  2. Define closeout before configuring synchronization
  3. Choose the order and shipment origin
  4. Map stores, carriers, packages, and warehouses
  5. Trace an order from export to acknowledgment
  6. Distinguish a label from a shipped parcel
  7. Bring tracking back to the correct ERP document
  8. Handle two packages on one order
  9. Control partial quantities and backorders
  10. Prevent premature invoice preparation
  11. Design customer notifications around partial fulfillment
  12. Reconcile carrier charges and freight
  13. Treat label voids and edits as exceptions
  14. Monitor failures, timing, and duplicate events
  15. Run a shipment acceptance test matrix
  16. Use a controlled go-live and daily closeout review
  17. Frequently Asked Questions
  18. Sources

Which ShipStation–Acumatica integration is in scope?

Start by identifying the actual integration package. Biz-Tech Services describes its ShipStation Connector as a native Acumatica extension with a store configuration, selectable data direction, status mapping, shipping-method and warehouse cross-references, and shipment workflows. Separately, ShipStation publishes an Acumatica store integration guide with its own customization packages, supported versions, and documented limitations. These are distinct sources. Do not carry a setting, supported version, or limitation from one package into the other without checking the installed build.

Record the Acumatica release, connector vendor, package version, selected store, ShipStation account, and any custom code. Ask the implementation team which package owns order export, shipment import, label notification, and invoice status. If multiple solutions or custom middleware touch the same order, assign one source of truth for each event. Otherwise, a correct label can still produce two competing updates.

The purpose of this guide is an operations and validation plan for the Biz-Tech workflow. ShipStation’s own documentation is used for general ShipStation behavior and as a reminder to confirm compatibility, not as proof that every Biz-Tech connector build behaves identically.

Back to TOC

Define closeout before configuring synchronization

“Complete” can mean different things to a warehouse lead, the order manager, and finance. The warehouse may mean all labels were printed; customer service may mean the carrier accepted every parcel; finance may mean the ERP order is ready for invoice. Write the business definition first. For each order line, compare ordered quantity, cancelled quantity, shipped quantity, and remaining authorized quantity. For each package, identify the carrier, service, tracking number, and shipment record. Then decide which of those facts must exist before the next ERP action is allowed.

A useful closeout invariant is: no unaccounted quantity and no unaccounted package. For example, an order of ten units that ships as six now and four later should not be treated as a fully shipped order merely because the first six have tracking. The remaining four must be backordered, cancelled under an approved rule, or represented in another open shipment. Likewise, two boxes containing all ten units need two package records if the carrier issued two tracking numbers and the connector supports that representation. This is an editorial control rule, not a claim about an automatic software status.

Create a short sign-off sheet: expected quantity, shipped quantity, open quantity, package count, tracked package count, ERP shipment status, ShipStation shipment status, carrier handoff status, and invoice decision. Make the owner of each exception visible.

Back to TOC

Choose the order and shipment origin

Biz-Tech’s product page describes two directions: Acumatica to ShipStation for ERP orders exported for fulfillment, and ShipStation to Acumatica for orders imported from the shipping platform. It also describes shipment processing either in ShipStation with results imported to Acumatica or through Acumatica shipment confirmation. Biz-Tech ShipStation Connector. These are materially different operating models. Write down the selected one before testing any closeout rule.

In the ERP-origin flow, Acumatica is the primary order record. The team exports a sales order, receives a downstream identifier, fulfills it, then returns shipment and tracking data. Biz-Tech’s data-flow lesson identifies the ShipStation Order ID on the Acumatica sales order as evidence that the export succeeded. An order with an empty ID needs investigation before the warehouse assumes it has a usable shipping job.

In the ShipStation-origin flow, a selling channel may feed the shipping platform first, and the connector imports an order into Acumatica. The import status, document type, customer rule, item rule, and beginning date become part of financial control. A shipping event cannot close an ERP order that was never created or that mapped to the wrong customer. Separate the two flows in your test evidence; a successful one-way test does not prove the reverse direction.

Back to TOC

Map stores, carriers, packages, and warehouses

For each store, list the external store ID, Acumatica store code, warehouse, ship-from location, default carrier, service, and package type. Test a normal order and an order that intentionally uses a different warehouse or service. Biz-Tech’s connector page describes shipping-method and warehouse cross-references, and its data-flow lesson describes pulling carriers, packages, and warehouses into the Acumatica setup. Biz-Tech connector; data-flow lesson.

Do not treat similar names as a mapping. “Ground” might refer to several carriers; “Warehouse 1” might be a pickup point in one system and a stock location in another. Use the actual codes and a business owner who can approve the match. Include the fallback when a carrier or service appears in ShipStation but has no Acumatica cross-reference: stop, map, or route to a review queue. Silent defaults can make freight and service-level reporting wrong even when tracking appears.

Package configuration matters independently of carrier mapping. ShipStation’s Acumatica integration documentation says an Acumatica shipment without a package can receive a status update but no tracking number. That is a documented limitation of ShipStation’s own package and a useful test case for any implementation; verify it against the Biz-Tech build before treating it as its rule. ShipStation Acumatica help.

Back to TOC

Trace an order from export to acknowledgment

Use one sample order and record each identifier: Acumatica order type and number, ShipStation store and order ID, ERP shipment number, package ID, label ID if exposed, carrier, and tracking number. The order number alone may be shared by several shipments. A reference chain allows support staff to determine whether the failure happened before export, after label creation, during tracking import, or at invoice preparation.

Biz-Tech’s existing order-flow lesson describes export from a processing screen or an action on the Sales Orders screen, then the returned ShipStation Order ID. The new check is not whether a user clicked Export; it is whether the downstream ID matches the intended store and order. Keep a screenshot or report row for the sender, receiver, timestamp, and result.

If an export is retried, do not assume that an earlier attempt made no downstream record. Search by the stable order reference before replay. A retry policy should distinguish a transport timeout from a rejected order and an order that succeeded but failed to return an acknowledgment. Those cases require different remedies and can create duplicates if treated alike.

Back to TOC

Distinguish a label from a shipped parcel

ShipStation explains that label creation requests a carrier label, creates a shipment record, updates the shipment status, and may notify the selling channel. For a split order, the overall order can remain awaiting shipment until its other shipments also have labels. ShipStation label and split-shipment behavior. These application events do not by themselves prove that a parcel was physically handed to the carrier.

For closeout design, keep three checkpoints separate: label created, carrier accepted or scanned, and delivered or exception. Some businesses invoice at label creation; others require pick confirmation or carrier handoff. Neither choice is universally correct. Define the contract, risk, and customer communication policy that justifies it. ShipStation’s tracking dashboard distinguishes “Not Yet In System,” in transit, delivered, exception, and unknown statuses for supported carriers. Those statuses are useful for after-shipment monitoring, though the ERP connector may not import all of them.

If a label is printed and then voided, both the shipping platform and ERP records need review. Do not let the existence of an old tracking number satisfy a current closeout check.

Back to TOC

Bring tracking back to the correct ERP document

The key control is a match between a ShipStation shipment and the right Acumatica order and shipment. Biz-Tech’s data-flow lesson describes an import screen or Sales Orders action that brings back shipment and tracking data and moves the order toward Prepare Invoice in its documented primary flow. Verify that the imported package, carrier, and tracking number are on the expected ERP shipment, not merely visible somewhere on the order.

Test a single package first, then a second package with a different carrier or service. Look for the tracking value, shipping method, ship date, warehouse, quantity, and external shipment ID. If one field is absent, record whether it is an unsupported mapping, a failed import, or an optional field. An order-level status alone is too coarse to prove package-level accuracy.

The shipping team should know which screen proves each stage: a ShipStation shipment record for label and tracking, an Acumatica shipment record for imported fulfillment, and the sales order for the billing state. Give customer service a direct path to both systems when a buyer says “the tracking link does not work.”

Back to TOC

Handle two packages on one order

Two packages are not always a partial order. They may contain all ordered units split for size or carrier limits. Conversely, one package can be a genuine partial shipment if it contains only some units. The closeout test should measure quantities and package completeness separately.

ShipStation’s Split Ship guidance describes dividing items or quantities into shipment records, each with its own details. It advises checking whether the selling marketplace supports partial fulfillment statuses; otherwise a marketplace may tell the buyer the whole order shipped after the first parcel. That is a customer-experience test as well as an ERP test. Confirm the behavior of your storefront, ShipStation notifications, and installed Acumatica connector together.

ShipStation’s Acumatica help also documents that its own package has limitations around splitting orders in Acumatica and importing split orders. The guide attached to that help separately discusses partial-shipment support in certain package versions. Because the documentation covers version-specific packages and can be updated, do not generalize one sentence into a capability promise for the Biz-Tech connector. Ask for a live demonstration with your exact release and package. ShipStation Acumatica help.

Back to TOC

Control partial quantities and backorders

Use a numerical test that everyone can audit. Suppose an order has line A of eight units and line B of four. The first shipment contains five of A and all four of B; a later shipment contains the remaining three of A. After the first label, the expected state is: ordered 12, shipped 9, open 3, one tracked shipment, no full-order closeout. After the second label, shipped becomes 12 and open becomes zero. A cancellation would reduce the remaining authorized quantity instead. Put those numbers in both systems’ reports and see whether the connector creates the intended ERP shipment records.

Acumatica order type, ship-complete rules, and backorder policy can change the result of a partial import. The ShipStation Acumatica user guide describes an option in its package to support partial/split shipments by changing how a Ship Complete order is treated. That is not proof of an equivalent setting in the Biz-Tech connector. Verify your actual configuration and have the order manager approve the policy before launch.

Test a split made before export, a split made in ShipStation, and a late stock shortage. Document what can still be edited after export. If one system stops accepting changes after a split, the business needs a controlled manual correction route rather than repeated blind synchronization.

Back to TOC

Prevent premature invoice preparation

In Biz-Tech’s documented ERP-origin workflow, returning shipment data advances the order to Prepare Invoice. Biz-Tech data-flow lesson. For a partial order, that transition should be examined against the order type’s billing policy. It may be correct to invoice each shipped portion; it may be correct to wait for all shipments. The rule belongs to finance and operations, not to a generic “shipped” label.

Define the evidence required to invoice: line quantities, shipment confirmation, tracking, freight amount, tax basis, and any customer commitment. Then test that one shipment does not cause the remaining quantity to disappear or be invoiced twice. If the sales order moves to Prepare Invoice after a partial import, determine whether that means a partial invoice is intended, and ensure a second shipment can still be processed.

ShipStation’s own Acumatica documentation warns against preparing an invoice for a split order before all items or packages have shipped and received tracking in its documented workflow. Apply that warning to its package as written; use it as a risk prompt when validating a different connector, not as an automatic rule for all installations. ShipStation Acumatica help.

Back to TOC

Design customer notifications around partial fulfillment

Identify which system sends the shipment email, when it sends it, and whether it names one parcel or the whole order. ShipStation documents shipment-level notifications and warns that some marketplaces may report the whole order fulfilled after a partial shipment. ShipStation Split Ship guidance. Test the actual customer email and storefront order page, not only the internal dashboard.

For the twelve-unit example, the first email should accurately describe nine units or the first shipment, and the second should describe the remaining three. If the email says “your order has shipped” without context, customer service may receive avoidable contacts. If both ShipStation and a storefront send messages, check for duplicates and conflicting tracking links.

Keep the customer-facing promise aligned with the ERP status. “Label created” and “carrier has your parcel” are different claims. Choose wording that matches the event you can prove.

Back to TOC

Reconcile carrier charges and freight

Shipping cost is not always the same as the freight charged to the buyer. The actual carrier label amount, negotiated rate, insurance, surcharge, and customer charge may differ. Assign ownership for each field and decide whether an imported carrier fee is posted as cost, informational data, or part of another financial workflow.

ShipStation’s Acumatica integration reference lists carrier fee among shipment-notification data for its own package. Biz-Tech’s public connector page discusses carrier and shipping-method mapping, but does not itself establish every freight accounting treatment. Confirm the installed field mapping and trace one package through label fee, ERP shipment, sales order freight, invoice, and general ledger if applicable.

Include a split order with two carrier labels in the test. Ensure the combined cost is neither lost nor counted twice, and that a voided label’s fee treatment is reviewed separately.

Back to TOC

Treat label voids and edits as exceptions

A label void, address change, cancelled order, or post-export quantity edit can make the two systems disagree. ShipStation’s own Acumatica help says that changes after export do not automatically synchronize in that package and lists manual correction steps for voids and cancellations. The Split Ship guide says marketplace updates stop for an order after it is split in ShipStation. These are strong reasons to test edit timing and to document an exception owner.

Write a reversal runbook: who voids the label; who changes the ERP shipment; who checks the storefront; who tells the buyer; and how a replacement tracking number supersedes the old one. An old tracking number should remain auditable but should not appear as the active parcel. For a cancellation after partial shipment, preserve the completed shipment and cancel only the unshipped quantity under an approved business rule.

Do not re-export the entire order merely because one package needs a corrected label. First determine which external identifiers already exist and which document can safely be updated.

Back to TOC

Monitor failures, timing, and duplicate events

Create a daily exception view with exported orders lacking a downstream ID, ShipStation shipments lacking an ERP match, packages without tracking, orders with shipped quantity below ordered quantity, carrier-service mapping failures, and items awaiting invoice decision. Record the age of the oldest unresolved item. These measures reveal a stalled handoff before a customer reports it.

Time-zone alignment deserves a specific test. ShipStation’s Acumatica help notes that mismatched server and store time zones can shift order dates or cause late-day orders to be skipped by an import process in its package. For any connector, test orders just before and after local midnight and record timestamps with offsets. Do not infer that a missing order is absent until the import window and filters are checked.

Define idempotency for retries: the same external order ID must not create a second sales order, and the same shipment ID must not add a duplicate package. If the connector logs a failure, capture the external ID and error before pressing retry. A transport timeout can hide a successful remote write.

Back to TOC

Run a shipment acceptance test matrix

Use a representative set of orders in a test environment. Record expected and actual order, shipment, package, tracking, quantity, status, freight, and invoice outcomes for each case. At minimum, test:

  1. One order, one package, one carrier, and one tracking number.
  2. One order, two packages containing all units, with two tracking numbers.
  3. A true partial shipment with an explicit open or backordered quantity.
  4. A split order with different carrier services and warehouses.
  5. A label printed and voided before carrier handoff, then replaced.
  6. A post-export address or quantity correction requiring the approved exception path.
  7. An imported shipment with an unmapped carrier or package type.
  8. A late-night order across the configured time-zone boundary.
  9. A repeated shipment notification or retry after a timeout.
  10. A carrier tracking exception after ERP invoice preparation.
  11. A customer notification for the first parcel and another for the second.
  12. The finance closeout check for partial billing, full billing, freight, and remaining quantity.

Each test needs an evidence row and an owner. Mark a case passed only after the intended records are visible in both systems and the customer-facing result is acceptable. “The API returned success” is not enough when the ERP shipment or storefront status is wrong.

Back to TOC

Use a controlled go-live and daily closeout review

Begin with a small group of stores, warehouses, carriers, and order types. Freeze mapping changes during the first live cycle, keep manual dispatch capacity, and name the person who can pause a failing flow. Compare the first day’s ShipStation shipment count and package count with Acumatica shipment and package records, then compare ordered, shipped, cancelled, and open quantities. Review the customer emails for one real split order before expanding volume.

The daily closeout review should answer four questions: Did every exported order receive an acknowledgment? Did every shipped package reach the correct ERP document with usable tracking? Does every order’s open quantity make sense? Is each invoice decision supported by actual shipment evidence? If any answer is no, hold the relevant closeout action and resolve the underlying record rather than forcing a status.

Biz-Tech Services can help scope a ShipStation shipping workflow assessment that tests these scenarios in the installed connector and Acumatica version. The next practical step is to bring one normal order, one two-box order, and one genuinely partial order to a joint operations-finance review and agree what “complete” means for each.

Back to TOC

Frequently Asked Questions

Is a ShipStation label enough to close an Acumatica order?

No universal rule says so. Label creation is an application event; the business must define whether closeout requires package tracking, carrier handoff, complete quantity, or another approved checkpoint.

Can one order have multiple tracking numbers?

ShipStation supports multiple shipment records for an order. Whether every tracking number maps to the intended Acumatica package depends on the connector build and configuration, so test it with a two-box order.

What is the difference between a two-box order and a partial shipment?

A two-box order may contain all ordered units. A partial shipment leaves an authorized quantity open or backordered. Reconcile quantities separately from package count.

When should finance prepare an invoice for a split order?

Use the company’s partial-billing policy and the actual ERP order type. Verify that the invoice covers only the intended shipped quantity and that remaining units stay open when appropriate.

What if a shipment has status but no tracking number?

Inspect the package record and mapping. ShipStation documents a package prerequisite for tracking in its own Acumatica integration; verify the behavior of the installed Biz-Tech connector separately.

Can an order be changed after it is exported?

The answer depends on the connector and workflow. ShipStation’s own Acumatica integration documents manual corrections after export. Establish a tested change path for the package you use.

Should ShipStation or the storefront send the shipment email?

Choose one owner for each notification and test split shipments. Some marketplaces may mark a whole order fulfilled after the first parcel, so customer text needs validation.

Which system owns carrier and warehouse mappings?

The implementation team should maintain approved cross-references between ShipStation and Acumatica codes. Biz-Tech’s connector page specifically describes shipping-method and warehouse mapping options.

How do we catch a shipment that failed to return to Acumatica?

Compare ShipStation shipment IDs and tracking against Acumatica shipment/package records, monitor unmatched or aging items, and retry only after checking for a partial prior success.

Are ShipStation’s Acumatica help-page limitations the same as Biz-Tech’s connector limitations?

Not necessarily. The help page describes ShipStation’s own customization packages and versions. Confirm the installed vendor, build, release, and specific flow before applying a limitation to the Biz-Tech connector.

Back to TOC

Sources

Back to TOC

Privacy Preference Center