Reference · built on requestOperator by FibricOrders & fulfillment

Tracking Sync

Matches warehouse shipments to unfulfilled storefront orders and proposes the fulfillment post with its tracking number.

Request accessPricing ↗

About

A warehouse or 3PL ships an order and records the tracking number in its own system. The storefront still shows the order unfulfilled until someone posts that number back. Tracking Sync reads shipment events on the warehouse side, such as ShipHero's Shipment Update webhook, ShipBob's order.shipped event, or a ShipStation shipment list, and reads the storefront's open fulfillment orders on the other side. It matches the two on the order reference and drafts the call the storefront needs: fulfillmentCreate in Shopify, a shipment in BigCommerce, or a ship call in Magento.

You review each draft and approve it. The customer's shipping notification then comes from the storefront as usual. Orders the operator cannot match are listed by age so a person can resolve them.

This is a reference listing. It documents what Fibric would read from Tracking Sync and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shipment Update webhooks from ShipHero, with order_number, tracking_number, shipping_carrier, shipping_method, and the line items in each package
  • order.shipped and order.shipment.tracking.updated events from ShipBob, and each shipment's carrier and tracking_number
  • Shipments listed in ShipStation by orderNumber, with trackingNumber, carrierCode, serviceCode, shipDate, and the voided flag
  • Shopify fulfillment orders still open, and fulfillments whose trackingInfo has no number
  • BigCommerce orders with no shipment record, and Magento orders awaiting a shipment with tracks
  • Matches between the warehouse order reference and the storefront order number, and the ones that fail to match

Proposed actions

  • Target capability: propose a Shopify fulfillment through fulfillmentCreate with trackingInfo company, number, and url, and whether to notify the customer
  • Target capability: propose updating a Shopify fulfillment's tracking through fulfillmentTrackingInfoUpdate when a label was reprinted or replaced
  • Target capability: propose a BigCommerce shipment through POST /v2/orders/{order_id}/shipments with items, tracking_number, shipping_provider, and tracking_carrier
  • Target capability: propose a Magento shipment through POST /V1/order/{orderId}/ship with items, tracks, and the notify flag
  • Target capability: propose marking a ShipStation order shipped through POST /orders/markasshipped when the label was bought elsewhere

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Post 3PL tracking to Shopify

    ShipBob fires order.shipped when the labels print. The operator matches reference_id to the Shopify order and proposes fulfillmentCreate with the tracking. You approve, and the customer gets Shopify's shipping notification.

    With ShipBob, Shopify

  • Close the gap between ShipHero and BigCommerce

    Each Shipment Update webhook from ShipHero becomes a proposed BigCommerce shipment with tracking_number and shipping_provider. Orders the store still shows unshipped after the warehouse shipped them are listed by age.

    With ShipHero, BigCommerce

  • Record external labels in ShipStation

    When a Magento order ships from a warehouse that does not print in ShipStation, propose markasshipped with the carrierCode and trackingNumber so both systems show the same state.

    With ShipStation, Magento

  • Fix a tracking number that changed

    A warehouse reprints a label, and the Shopify fulfillment still shows the old number. Propose fulfillmentTrackingInfoUpdate with the new one, notifying the customer only if you choose.

    With Shopify, ShipHero

Requirements

  • One warehouse or 3PL connector that reports shipments with tracking numbers, such as ShipHero, ShipBob, or ShipStation
  • One storefront connector with fulfillment write access, such as Shopify, BigCommerce, or Magento
  • A shared order reference: the storefront order number or id carried on the warehouse order
  • A person who approves the proposed fulfillments, one at a time or as a batch
Authentication
Each connected system's own credentials, granted as that connector's listing describes; the storefront credential needs fulfillment write access, such as Shopify's write_merchant_managed_fulfillment_orders scope.

Limits

  • ShipStation lists only shipments with labels bought in ShipStation; orders marked shipped by hand or by API are external and do not appear
  • Shopify fulfillmentCreate needs the fulfillment orders to belong to one order and one assigned location; a split across locations means two proposals
  • BigCommerce accepts tracking_carrier only as an empty string or a supported courier slug, so an unknown carrier posts without one
  • A warehouse order that carries no storefront order reference cannot be matched and is listed for a person to resolve

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Tracking Sync ↗

Questions and answers

What does the approver see for each shipment?
One proposed fulfillment per shipment: the storefront order, the line items and quantities, the carrier, the tracking number, and whether the customer is notified. You can approve them one at a time or as a batch. Nothing posts until approved.
What is kept after a fulfillment posts?
Each proposal keeps the warehouse event it came from, the storefront call it made, the response, who approved it, and when. If the fulfillment was wrong, the record shows what to update or void.
Does it ever post a fulfillment on its own?
No. It reads shipments and orders and drafts the fulfillment. A person approves every post. It does not buy labels, change addresses, or cancel anything. If the same tracking number arrives twice, it proposes once and flags the second.
Ask about Tracking Sync

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy