Skip to content
ShipmentVisibility

Shipment tracking integrations for the systems you already run

ShipmentVisibility gets tracking numbers from the systems where your orders and loads already live and sends status back to the places your team works. Connect a Shopify store, an ERP or a file feed, route alerts to email, Slack or webhooks, and build your own connection with the REST API. Below is what each integration syncs and which plan includes it.

See pricing

Every integration at a glance

IntegrationWhat comes inWhat goes outPlan
Email alertsDelay and exception alerts to your teamStarter and up
CSV upload and exportTracking numbers with your referencesFull shipment list with status and ETAStarter and up
ShopifyOrders, fulfillments and tracking numbersBranded tracking links and shopper notificationsGrowth and up
SlackException and ETA change alerts to a channelGrowth and up
WebhooksShipment events to your endpointGrowth and up
NetSuiteItem fulfillments, sales and purchase orders with tracking numbersStatus, delivery date and ETA on the recordPro and up
SAP Business OneDeliveries and purchase orders with tracking numbersStatus and delivery datePro and up
Microsoft DynamicsShipments and orders with tracking numbersStatus and delivery datePro and up
CSV and SFTP feedsScheduled files from any ERP, TMS or WMSScheduled status files back to your serverPro and up
REST APIShipments from any systemShipments, events and ETA on requestPro and up

Shopify for ecommerce brands

Connect your store once and every fulfillment with a tracking number is added to your shipment list automatically. Shoppers receive a link to your branded tracking page in their shipping email and get notified when a parcel is delayed, out for delivery or delivered. Details and setup steps are on the Shopify order tracking app page.

ERP integrations with NetSuite, SAP Business One and Microsoft Dynamics

On Pro and Enterprise, ShipmentVisibility reads tracking numbers from the ERP records your team already fills in and writes status back, so buyers and customer service see the delivery status without leaving the ERP. Inbound freight works the same way: put the container number, bill of lading or PRO on the purchase order and you see the ocean milestones, last free day and LTL delivery against the PO.

  • NetSuite: item fulfillments and sales orders for outbound, purchase orders for inbound, status and dates written to fields you choose
  • SAP Business One: deliveries for outbound and purchase orders for inbound, with status and delivery date returned
  • Microsoft Dynamics: shipments and orders with tracking numbers, status and delivery date returned
  • Your references (order, PO, customer) travel with every shipment into alerts and the tracking page

CSV and SFTP feeds for any TMS or WMS

Not every system has a modern connector, and many TMS and WMS platforms already export files. On every plan you can upload a CSV of tracking numbers in the dashboard and export your list with status and ETA. On Pro, an SFTP feed picks up files on a schedule you set and drops status files back on your server, so an older system stays in sync without code.

  • Columns for number, optional mode or carrier hint, ship to ZIP and your references
  • Carrier detected from each number format, invalid numbers reported per row
  • Scheduled status files with latest milestone, delivered date and predicted ETA

Email, Slack and webhook alerts

Alerts go where the right person will see them. Email alerts for delays and exceptions are on every plan. Growth adds Slack, so an exceptions channel can show every OS&D, rolled container or failed delivery attempt as it happens, and webhooks, so your own systems can react. Webhook event types are shipment.updated, shipment.exception, shipment.delivered and eta.changed.

REST API when you want your own integration

If your order system, customer portal or data warehouse needs tracking data directly, the shipment tracking API on Pro and Enterprise gives you endpoints to add shipments, read their status and read their event history in one normalized model for every mode. One API replaces separate integrations with each parcel carrier, LTL carrier, ocean line and airline.

How connecting works

  1. 01Create your account and choose a plan that includes the integration you need.
  2. 02Open Integrations in the dashboard and connect the store, ERP, Slack workspace or SFTP folder.
  3. 03Map your references, such as order number, PO or customer, so they appear on alerts and tracking pages.
  4. 04New shipments start appearing in your list as soon as they have a tracking number.

There is no implementation project and no sales call. For a complete evaluation checklist see supply chain visibility software, and for multi-modal tracking see the freight visibility platform.

Shipment tracking integrations questions

Which plan do I need for integrations?

Email alerts and CSV upload and export are on every plan. Shopify, Slack and webhooks start on Growth. NetSuite, SAP Business One, Microsoft Dynamics, SFTP feeds and the REST API start on Pro.

Do I need a developer to connect an ERP?

No. The ERP connectors and SFTP feeds are set up in the dashboard. A developer is only needed if you want to build your own connection with the REST API.

Do synced shipments count against my plan?

Yes. Every shipment added in the billing period counts once, whatever the source. Deleting a shipment does not return quota.

Can I use more than one integration at a time?

Yes. Many teams connect Shopify for parcels and an ERP or SFTP feed for freight, and all shipments land in the same list.

Does the integration change my carrier setup?

No. Carriers, accounts and rates stay as they are. ShipmentVisibility reads tracking numbers and returns status.

Connect the systems you already have

Start with a single number to see how ShipmentVisibility reads it, then connect your store or ERP.

See pricing