HOW-TO · Expédition

Comment automatiser la sync tracking vers les marketplaces

Arrêtez de copier les numéros de suivi dans chaque portail vendeur. Utilisez ChannelDock Shipping Rules pour relier création d’étiquette, tracking transporteur et mises à jour marketplace dans un seul workflow. Shipping Rules.

Utiliser Shipping RulesCommencer gratuitement
Créer les étiquettes
Capturer le tracking
Capturer le tracking
Synchroniser les mises à jour
Synchroniser les mises à jour
bol.com · Amazon
Aperçu de sync trackingPrêt à envoyer
bol.com order · PostNL3S...
Amazon order · DHLJVGL...
Shopify order · DPD0516...
Blocage : code transporteur manquant

Tracking sync matters because marketplaces judge shipment quality from scan events, carrier codes and on-time updates. A clean workflow prevents late-upload warnings, buyer questions and duplicate portal work.

Fewer portal updatesno copy-paste loops
Cleaner evidencetracking on the order
Faster buyer updatesshipment status shared
Exception controlfailed syncs visible

Avant de commencer : ce qu’il faut préparer

Prepare the data first. Tracking automation only works when orders, labels and carrier services use the same identifiers.

Connected marketplaces

Make sure bol.com, Amazon, Shopify or other marketplaces are connected and importing orders into the same ChannelDock order flow.

Carrier label workflow

Create labels through a connected carrier or shipping integration so the tracking number, carrier name and service code are captured automatically.

Permission to update shipments

Use an account that may mark orders as shipped and send tracking updates back to each sales channel.

Tip: test with one low-risk marketplace first. Once tracking updates arrive correctly, copy the same pattern to the channels with stricter shipment SLAs.

Pas à pas : automatiser la sync tracking marketplace

Use this sequence to move from manual tracking uploads to a controlled post-shipment update workflow.

Map each channel’s shipment requirements

List the marketplaces you sell on and note what each one expects: carrier name, carrier code, tracking number, tracking URL, shipment time and partial-shipment support.

Common mistake: assuming every marketplace accepts the same carrier names. Amazon, bol.com and local marketplaces often use different carrier-code formats.

Create labels from the order record

Print labels from the ChannelDock order or pick-pack flow instead of an external portal. That keeps the label, tracking number and order ID connected. multi-carrier label workflow.

Common mistake: printing labels outside the order flow, then trying to match tracking numbers later by customer name or postcode.

Standardize carrier and service names

Use Shipping Rules to select the right carrier service and keep naming consistent before tracking data is sent to marketplaces. Shipping Rules.

Common mistake: letting packers type free-text carrier names, which causes rejected tracking uploads.

Send tracking updates after dispatch

Trigger the shipment update when the parcel is packed or manifested, so the marketplace receives the tracking number only after the label is final.

Common mistake: sending tracking before the label is actually used, creating cancelled or duplicate shipment events.

Monitor failed syncs daily

Review orders where tracking was not accepted, fix the carrier mapping or address issue, and resend the update before marketplace deadlines.

Common mistake: treating sync failures as IT noise instead of operational exceptions that can affect seller metrics.

Audit tracking evidence after busy days

After peak days, compare shipped orders with marketplace shipment status to catch missing tracking before buyers open support tickets.

Common mistake: only checking the carrier portal, while the marketplace still shows the order as unshipped.

Le flux de sync tracking en bref

The safest workflow creates one shipment record, attaches the carrier tracking number and sends the same evidence to every channel that needs it.

Tracking sync is not an admin afterthought. It is the proof that the marketplace, the buyer and the warehouse are looking at the same shipment.

Order packed
Label created
Tracking captured
Marketplace updated

Erreurs fréquentes de sync tracking

  • Using carrier names that do not match the marketplace’s accepted carrier-code list.
  • Uploading tracking before the parcel is packed, then cancelling or reprinting the label.
  • Forgetting partial shipments, so one tracking number is sent for an order that leaves in multiple parcels.
  • Printing labels in carrier portals and losing the link between order ID and tracking number.
  • Not reviewing rejected shipment updates before marketplace cutoff times.

Uploads tracking manuels vs. ChannelDock Shipping Rules

Manual uploads can work for a handful of orders. They break down when order volume, carriers and marketplace rules increase.

Sans ChannelDock

  • Packers copy tracking numbers from carrier portals into each marketplace manually.
  • Carrier names, shipment times and partial shipments are handled differently by each operator.
  • Failed uploads are noticed only when buyers ask for tracking or a marketplace warning appears.

Avec ChannelDock

  • Tracking numbers stay attached to the order as labels are created and shipped.
  • Shipping Rules standardize carrier/service choices before the update is sent.
  • Operations can review exceptions and keep marketplace shipment evidence in one workflow.

Explore Shipping Rules →

FAQ sur la sync tracking marketplace

Create labels from the order record, capture the tracking number automatically, map the carrier service correctly and send shipment updates back to each connected marketplace from one workflow.

Most major marketplaces, including bol.com and Amazon, expect shipment confirmation with tracking details when the carrier service supports it. Requirements vary by channel and delivery promise.

You need the order ID, carrier name or code, service, tracking number, shipment timestamp and sometimes a tracking URL or parcel-level split for partial shipments.

Send tracking after the final label is created and the parcel is ready for dispatch. Sending too early can create cancelled labels, duplicate events or incorrect buyer updates.

Keep each parcel tied to the right order lines and send parcel-level tracking when the marketplace supports it. If it does not, add an internal exception process.

The most common causes are invalid carrier codes, missing tracking numbers, unsupported service names, address errors, duplicate shipment updates or shipment timing that violates marketplace rules.

Workflows liés à améliorer ensuite

Once tracking sync is stable, tighten the workflows around labels, carrier decisions and order processing.

Print shipping labels

Create labels and tracking evidence from one order workflow.

Lire le guide

Set up shipping rules

Route orders by weight, destination and delivery promise.

Lire le guide

Compare carrier rates

Balance carrier cost with marketplace service expectations.

Lire le guide

Manage marketplace orders

Keep order status, fulfillment and exceptions in one dashboard.

En savoir plus

Synchronisez automatiquement les numéros de suivi après chaque expédition

Use ChannelDock Shipping Rules to keep labels, tracking numbers and marketplace shipment updates connected from order to dispatch.

Voir Shipping RulesCommencer gratuitement