Advanced Shipment Tracking Pro - WordPress Plugin

Guide to Configuring and Using Advanced Shipment Tracking Pro

Advanced Shipment Tracking Pro gives a WooCommerce store more than just a place to save a tracking number in the order. The plugin's real job is to turn scattered data from carriers, label printing services, CSV files, and external warehouse systems into a clear post-purchase workflow: the order gets a tracking number, the customer sees a link in the email and account area, the manager understands the fulfillment status, and disputed orders can be verified faster.

This guide walks through practical setup after installation: which statuses to enable, how to prepare carriers, when to use partial shipments, how to import tracking numbers in bulk, what to check in WooCommerce emails, and where to look when something goes wrong. It is written for store administrators who already work with WooCommerce and want a controlled shipping workflow without chaos in order notes.

This guide does not repeat the short product description. What matters here is something else: how to use Advanced Shipment Tracking Pro in a real operating workflow, which settings should be enabled carefully, what to verify on a test order, and when the plugin should be paired with a delivery monitoring service.

What Problem the Plugin Solves in WooCommerce

In standard WooCommerce, an order moves through payment, processing, fulfillment, and completion, but the platform does not always give the store a clean layer for managing tracking numbers. If a manager simply leaves the shipment number in an order note, the customer may never see it, the email may go out without a clear tracking button, and support will still get delivery questions. Advanced Shipment Tracking Pro closes that exact gap between the moment an order ships and the moment the customer gets clear confirmation.

The plugin adds structured shipment data to the order: carrier, tracking number, ship date, fulfillment status, and, if needed, a customer note. That data is then used in the tracking widget, WooCommerce emails, the customer's account area, the fulfillment dashboard, CSV import, REST API, and payment service sync. It should be treated as an operational discipline layer, not as a decorative "Track" button.

The real value appears when tracking stops being a manual note and becomes part of the order status. The manager selects a carrier from the enabled list, adds the number, marks the order as shipped or partially shipped, and the customer gets the message in a predictable place. If the store works with ShipStation, WooCommerce Shipping, Sendcloud, Printful, Shippo, EasyPost, or similar services, dedicated integrations help move tracking data into the correct WooCommerce metadata instead of leaving it only in order notes.

Where the Plugin Is Especially Useful

Advanced Shipment Tracking Pro makes sense in stores where the tracking number matters not just to the manager, but also to the customer. That includes physical products, dropshipping, print-on-demand, warehouse fulfillment, international shipping, multi-box orders, and scenarios where a payment service or marketplace may request proof of delivery.

• The store ships a high volume of orders and wants to add tracking numbers in batches through CSV or API.
• A single order may be split into multiple packages, so partial fulfillment and item-level tracking are necessary.
• The customer should see the tracking number in the email and in My Account, instead of receiving a separate manual email from the manager.
• The warehouse or shipping system uses carrier names that differ from the AST list, so alias mapping is required.
• The store needs to sync tracking numbers to PayPal or Stripe so transactions reflect the shipment.

When the Product May Be Unnecessary

If the store sells only digital products, does not use carriers, and closes orders immediately after payment, a full shipment tracking layer may be unnecessary. It also does not replace a shipping rate system, label printing workflow, warehouse management platform, or a service that actively monitors delivery events from carriers. The plugin stores, displays, and passes tracking data along; monitoring a package based on carrier events usually requires a separate service such as TrackShip or another external logistics platform.

A practical rule: if customers need to see where their package is, and your team needs to know which orders have already shipped, Advanced Shipment Tracking Pro is worth evaluating. If the store does not ship physical items, first decide whether it would add process complexity without delivering real value.

What to Check Before Installation

Before installing the plugin, do not rush into every setting at once. First map out your current shipping process. Where does the store get the tracking number from: the carrier dashboard, ShipStation, a supplier CSV, the warehouse, an ERP, WooCommerce Shipping, or manual entry? Who changes the order status? Should the customer receive an email as soon as the tracking number is added? Do partial shipments happen? Those answers determine which plugin panels you should touch first.

Check compatibility at the workflow level. The store may already have plugins for email customization, multi-vendor setups, custom order numbers, PDF invoices, SMS notifications, order export, dropshipping integrations, and payment gateways. With Advanced Shipment Tracking, technical compatibility is only part of the picture. You also need to decide which tool is the source of truth for tracking. If two tools change order statuses, send emails, and add notes at the same time, the customer may get duplicates or conflicting messages.

Quick Preparation Checklist

• Create a backup of the site and database before changing order statuses and email templates.
• Prepare a test physical product, a test customer, and a test order with a real or demo tracking number.
• Make a list of the carriers the store actually uses, including local and international delivery services.
• Check which plugins already add tracking to orders or send shipping emails.
• Decide whether you will use manual entry, CSV, API, integrations, or a mixed approach.
• If you plan to use PayPal or Stripe sync, prepare test mode and logging, but do not store secrets in public notes or helper prompts.

The most common early mistake is turning on all statuses, emails, integrations, and auto-import at once, then trying to understand why the customer got the wrong notification. It is much safer to start with one test order, one carrier, and one notification channel, then gradually add bulk operations.

Installation and Initial Validation

The overall installation path is standard for a paid WordPress plugin: upload the ZIP file through Plugins - Add New - Upload Plugin, install it, and activate it. After installation, the settings are available in the admin panel under WooCommerce - Shipment Tracking. Zorem's documentation separately notes that the Pro version is standalone and may deactivate the free AST plugin if it is already installed. That is a normal migration scenario, but before doing it, you should confirm that the existing tracking data is still visible in orders.

This guide does not cover purchasing, payment, or license activation. For a real deployment, what matters more is verifying right away that the plugin can see WooCommerce orders, opens its settings panels, and allows you to enable a carrier. If the interface does not appear in the WooCommerce menu, first check the user role: managing orders usually requires an administrator account or a role with WooCommerce permissions.

Post-Activation Check

1. Open WooCommerce - Shipment Tracking and make sure the settings pages load without errors.
2. Go to Shipping Carriers and enable 1-2 carriers that the store actually uses.
3. Open a test order with the Processing status and find the tracking info block or action.
4. Add the shipment number, select the carrier, and save the changes.
5. Verify that the information appears in the order, the customer email, and My Account on the front end.

Safe Rollback During Testing

If emails start going out in unexpected ways after enabling the plugin, do not immediately delete it from the live site. First disable email sending for the questionable status in the Order Statuses & Notifications panel, remove automatic status changes during import, and test one order. This kind of rollback preserves the order data and gives you a chance to identify which setting caused the side effect.

Carriers, Aliases, and Custom Tracking Links

In Advanced Shipment Tracking Pro, the carrier list is not just a decorative directory. It determines which values the manager sees in the dropdown, how the tracking link is built, and whether an import from an external system can match the carrier name to what the plugin expects. According to Zorem's documentation, carriers are not enabled by default after the first installation, so they need to be added through WooCommerce - Shipment Tracking - Shipping Carriers.

How to Enable Carriers Without Filling the List With Noise

Do not enable hundreds of carriers "just in case." The shorter the active list, the fewer manual selection mistakes you will get, and the easier it will be to train your team. A typical store only needs the main services the warehouse actually uses, plus 1-2 backup options. If the store works with international suppliers, separately review carriers used in dropshipping logistics: ePacket, Yanwen, Yun Express, China Post, 4PX, and similar services often differ from local couriers.

After adding carriers, run a test: create a tracking entry with each primary carrier and click the tracking link. If the link opens the carrier page without inserting the tracking number, you need to check the URL template or select the correct carrier from the list. For a custom carrier, the documentation describes the fields Carrier Name, Custom Display Name, Country, logo, and Custom URL. In the custom URL, you can use variables such as %number%, %postal_code%, and %country_code%.

Why API Aliases Matter

Your warehouse system, label service, or CSV supplier may refer to the same carrier under a different name. For example, the source may send USPS Priority, while AST names the carrier USPS. Without proper mapping, the plugin may fail to recognize the carrier, causing the import to fail or preventing the tracking number from appearing in the correct widget. That is what the Custom API Name field in the carrier record is for.

Aliases need to match the source exactly. If the CSV sends US Postal but the alias is entered as USPS Postal, do not expect the system to guess. Collect the real values from CSV files or API responses, add them to the carrier record, and test the import on 2-3 rows before launching a large batch.

When to Use Sync Carriers

The Sync Carriers tool updates the built-in carrier database, including names, logos, and tracking URLs. It is useful if a carrier appears in the documentation but is missing from your local database, or if a carrier's tracking link has stopped working. The Reset carriers database option requires caution: the documentation warns that it clears enabled and custom carriers. On a live store, this action should only be used after exporting the settings or at least documenting the carrier list, so you do not have to rebuild everything manually later.

Order Statuses and Emails: Where the Customer Experience Is Defined

The most important part of setup is not the widget design. It is the relationship between the order status and the notification. In the Order Statuses & Notifications panel, you can manage statuses such as Partially Shipped, Shipped, and Delivered, status colors, email sending, and the transition away from standard Completed toward a clearer logic for physical order fulfillment.

For a store selling physical goods, the standard Completed status often sounds ambiguous: the order is complete in the system, but the customer may read it as "delivered." That is why AST supports a workflow where Completed can be renamed to Shipped, or where a separate custom Shipped status is used alongside Completed. The right choice depends on how your reports, integrations, and accounting processes are built.

Recommended Logic for a Typical Store

For most stores, it makes sense to start with a simple model. Processing means the order has been paid for or accepted and is waiting to be packed. Partially Shipped should be used only for orders where some items have already shipped and others are still waiting to go out. Shipped applies when all physical items have been sent and the customer should receive tracking. Completed can be kept for internal closure or skipped as a separate step if the store renames it to Shipped.

Do not automatically enable email for every status. Customers benefit from messages tied to real changes: the first part of the order shipped, the remaining items shipped, the delivery can now be tracked. They do not need internal duplicates coming from the warehouse, the payment gateway, and the email customizer. If the store already uses a separate SMS or WhatsApp notification plugin, check whether it sends a message for the same status.

Colors and Visibility in the Fulfillment Panel

Status color may seem like a minor detail until the store starts processing dozens of orders a day. According to AST Pro documentation, custom status rows support background and font colors. Use them for operational navigation, not decoration: partially shipped orders should stand out visually from fully shipped ones, and problematic or action-required orders should not blend in with normal processing.

What to Check After Saving Statuses

• The status appears in the order list and does not conflict with WooCommerce reports.
• The email is sent only on the intended transition, not every time the order is edited.
• The email copy does not imply delivery if the order has only been handed off to the carrier.
• A partial shipment does not close the order as fully fulfilled.
• The manager can see which items have already shipped and which remain pending.

Configuring the Tracking Widget and Emails

Once the statuses are working, you can move on to what the customer will actually see. The Email Customizer in AST Pro lets you configure the tracking widget, email content, and display options. According to the documentation, you open the customizer through the gear icon next to a status in the Order Statuses & Notifications panel. That makes sense, because different statuses may require different email messaging.

The tracking widget should be easy to understand, but not overloaded. The customer needs the carrier, tracking number, a button to open tracking, the shipment status, and, if needed, a short explanatory note. Everything else depends on the store brand and support policy. For example, for high-value products it can help to add a calm note that carrier updates may not appear immediately. For international shipments, you can add a note about possible delay between handoff and the first scan.

Settings Worth Configuring First

• Tracking header text - a short block heading, such as "Shipping Information" if the email is localized in English.
• Additional text after header - a careful note for the customer without promising an exact delivery timeframe.
• Tracker type - progress bar, icons, or single icon, depending on how much detail your process can actually support.
• Button text - a clear call to action that leads to the carrier tracking page.
• Background, border, button colors - colors that do not clash with the store's email template.
• Display product images and addresses - show only what helps the customer confirm the order and does not create unnecessary noise.

Dynamic Placeholders in the Email

Email content supports placeholders such as {customer_first_name}, {order_number}, {tracking_number}, {shipping_provider}, {shipping_date}, and {shipping_method}. Use them in moderation. A good email explains what changed and where to track the shipment; a bad email turns into a long printout of internal fields.

You can create a safe email message without writing code:

Your order {order_number} has been handed over for delivery. Tracking number: {tracking_number}. If the link does not show movement yet, check again later - carriers sometimes need time for the first scan.

After saving, send a test email to an internal address. Check not only the browser preview, but also a mobile email client. If the button is too wide, the text blends into the background, or the tracking block appears below a long promotional footer, the customer will still end up contacting support.

Adding Tracking Numbers Manually, Through CSV, and Through API

Advanced Shipment Tracking Pro supports several input paths for tracking data. Manual entry is convenient for a small store or an unusual shipment. CSV works when the warehouse or supplier sends a table with shipment numbers. The REST API is appropriate for an ERP, OMS, 3PL, an internal warehouse dashboard, or a label printing service. The goal is not to choose the "most advanced" method, but the one that produces the fewest errors in your process.

Manual Entry in the Order

The documentation describes three places where tracking can be added: the order list, the order edit page, and the Fulfillment Dashboard. The form typically requires Tracking Number, Shipping Provider, Date Shipped, an optional note, and a Mark Order As choice. If the order ships in full, choose Shipped. If only part of the order has shipped, use Partially Shipped and set quantities at the item level.

Partial shipment is especially important for orders fulfilled from different warehouses or containing made-to-order items. The first tracking number should not close the entire order if some items have not shipped yet. Otherwise, the customer will see "everything shipped," receive only one box, and contact support.

CSV Import for Bulk Fulfillment

CSV Import is useful when the warehouse sends a table at the end of the day with order ID, carrier, tracking number, date shipped, shipped status, and a note. The documentation emphasizes that the date format in the file must match the format selected during import, and the carrier must match an enabled carrier or alias. If the import fails, the system shows successful and failed rows, so do not upload a large table without testing a small batch first.

For tracking per item, the CSV can include sku and qty. That is helpful when one order is split by item. But this kind of import requires SKU discipline: if the warehouse uses one SKU and WooCommerce stores another, the partial shipment will be linked incorrectly or not linked at all.

REST API and the Bulk Endpoint

The REST API lets you add, retrieve, and delete tracking entries programmatically. The documentation lists required properties such as order_id, tracking_provider, tracking_number, date_shipped, and status_shipped. For larger flows, there is a bulk endpoint where the shipments array sends multiple shipments in one request. That reduces the number of API calls and is better suited to integration with external systems.

Do not publish your Consumer Key and Consumer Secret in documents, contractor tasks, or content-generation prompts. For testing, use a separate key with only the required permissions, and after the integration is complete, verify that old keys are not still sitting with a contractor or in a test Postman workspace.

Typical API Rollout Order

1. Create a separate WooCommerce REST API user or key with the minimum required permissions.
2. Enable AST API logs only during testing or troubleshooting.
3. Send one test order and verify the response with the tracking ID.
4. Check the customer email and the My Account block.
5. Check the duplicate tracking error and the behavior of replace_tracking.
6. Only after that should you enable bulk requests or regular synchronization.

Integrations With Shipping Services and Scheduled Import

One reason to choose the Pro version is not just the presence of a REST API, but readiness to work with real tracking data sources. Zorem's documentation lists integrations with label printing services, fulfillment platforms, shipping providers, and warehouse tools. The point of these integrations is that an external system can write tracking information into the proper shipment tracking metadata instead of just leaving an order note. That is critical for emails, the customer account, and downstream synchronization.

Before enabling any integration, it helps to understand how the specific service returns data. Some tools provide the tracking number and carrier immediately after the label is created. Others add a record to order notes. Still others export a CSV file at the end of the shift. Advanced Shipment Tracking Pro helps normalize those inputs into one structure, but it does not remove the need to validate the source. If the service writes the carrier as FedEx Express Saver while only FedEx is active in AST, you need an alias map. If the service exports dates in U.S. format while CSV import is configured for another format, some rows may fail.

How to Choose Between Integration, CSV, and API

An integration is convenient when your shipping service is officially supported and already knows how to send tracking data into WooCommerce. CSV is better for suppliers that do not have API access to your site but can export a table. REST API is the right choice when you control the external system or can have a developer build a direct data push. FTP/SFTP auto-import works well for a recurring flow where a file appears on the server on a schedule.

FTP/SFTP Auto-Import Without Unexpected Data Loss

Automatic import over FTP/SFTP looks simple: enable the schedule, enter the server URL, username, password, port, remote directory, and save. In practice, the risk lives in the details. The documentation points out that CSV Folder Path must be a remote folder, not a file name. If the path is wrong, the import may not find the files. If you enable Delete After Import before a successful test, you may lose the original file on the source side and make a re-import much harder.

Start by creating a separate test folder, place one CSV file with 2-3 rows there, and run Test Connection. After the connection succeeds, verify that the import completed, the tracking numbers appeared in orders, and errors were written to the logs. Only after that should you move the process to the live folder and agree with the supplier on who is responsible for file archiving. Ideally, the source should keep copies for at least a few days so a batch can be restored after an error.

Settings That Require Extra Caution

• Import Frequency: daily import is enough for most stores, but high-volume operations may need several batches a day through an external process or API.
• Import Time: choose a time after the warehouse has finished building the file, otherwise the site may import an incomplete export.
• FTP/SFTP Port: do not assume the default if the supplier gave you a different port.
• Delete After Import: enable it only after confirming that a copy of the file is stored at the source or in a separate archive.
• Enable Log: enable logging during rollout and troubleshooting, then keep log volume under control.

What to Do If the Shipping Service Writes Only to Order Notes

Some shipping tools historically add tracking information to order notes. For an administrator, that may seem acceptable because the number is visible in the order. But from the customer's perspective, that number may never appear in the tracking widget, the email, or the account area. AST Pro's product page specifically highlights this problem: tracking data needs to be stored as structured shipment tracking metadata, otherwise it stays trapped in the internal service layer.

If your shipping service already leaves a note, do not build automation around manually copying from the note into the tracking panel. Check whether AST Pro already offers a dedicated integration for that service. If not, evaluate CSV or API. For occasional shipments, manual copying is acceptable, but for a daily flow it quickly becomes a source of mistakes: the manager copies the wrong number, chooses the wrong carrier, or closes the order too early.

Validation Order for a Recurring Flow

1. Document the source: integration, CSV, FTP/SFTP, or API.
2. Align carrier names and add aliases before the first large batch.
3. Check the date format and shipped status on test rows.
4. Make sure the order status changes only in the expected cases.
5. Check the email and customer account for one full shipment and one partial shipment.
6. Agree on who fixes failed rows: the warehouse, the site administrator, or the integration developer.
7. Document the rollback plan: how to stop auto-import, how to remove an incorrect tracking entry, and where to review logs.

This process may feel slow, but it saves time in support. Scheduled tracking import is not a one-time setting. It is part of your operating workflow. If the workflow is not documented, every error will be rediscovered by a different person.

Fulfillment Dashboard and the Store Workflow

The Fulfillment Dashboard is there for operational control. It brings together orders that need fulfillment and helps the manager avoid bouncing between order list filters, the order edit page, and notes. In practice, this is especially useful when the store has multiple fulfillment statuses and some orders do not ship immediately.

The dashboard should not become just another place where the team loosely "checks orders." Configure General Settings so that only the necessary statuses appear in the fulfillment view, such as Processing and Partially Shipped. If you include every status, the dashboard loses its purpose and starts to look like a regular order list.

Practical Example: One Order, Two Packages

Goal: show the customer that part of the order has already shipped and the remainder will ship separately, without closing the order too early.

Preparation: the required carriers are enabled, the Partially Shipped status is active, emails for partial and full shipment are configured, and the test order contains two items with clear SKUs.

1. Open the test order in WooCommerce - Orders or through the Fulfillment Dashboard.
2. Click the action to add tracking info.
3. Select the carrier for the first package and enter the tracking number.
4. Specify quantities only for the items that have actually shipped.
5. Make sure Mark Order As is set to Partially Shipped.
6. Save the shipment and check the customer email.
7. When the remainder ships, add the second tracking number and mark the remaining items.
8. After full fulfillment, verify that the order moved to Shipped or another selected final status.

Checking the Result

Open the order in the admin panel and confirm that the shipment tracking panel shows two entries rather than one overwritten record. Then log in as the test customer and open My Account - Orders - order view. The customer should see clear information for each shipment. If the email or account area shows only the latest entry, check the multiple tracking numbers per order item setting and confirm that replace tracking was not enabled in CSV or API.

Bottom line: partial shipment works well only when the team carefully enters item quantities. If the manager keeps entering one tracking number "for the whole order" out of habit, the Partially Shipped status will not save the process.

PayPal, Stripe, and TrackShip: What to Enable Deliberately

The Pro version includes tracking data sync for PayPal and Stripe. According to the documentation, when an order is marked as Completed or Shipped, the plugin can send the tracking number, carrier, and status to the linked transaction. That is useful for stores where disputes, fund holds, or chargeback workflows require transparent shipment information.

But these integrations should not be enabled as if they were cosmetic settings. They interact with payment transactions, require API credentials, and may trigger additional customer notifications. That is why you should first check test mode, logs, and one sample order. In the PayPal panel, there are settings for sandbox, payment method selection, sending email from PayPal, and logs. The Stripe panel also includes payment method selection and logs. Turn logging on during troubleshooting, then disable it if it is no longer needed.

When You Need TrackShip in Addition

Advanced Shipment Tracking Pro adds and transmits tracking data. TrackShip handles shipment monitoring and carrier delivery events. These are different layers. If the store only needs to provide the customer with a tracking link, AST Pro may be enough. If you need automatic shipment status updates, movement notifications, a branded tracking page, and delivery performance analytics, TrackShip is worth considering as a companion product.

Do not confuse the WooCommerce order status with the real package status at the carrier. The Shipped status means the store handed the shipment off for delivery or added tracking. It does not guarantee that the carrier has already scanned the package, that it is moving, or that it has been delivered.

Safe Improvements and Support Discipline

AST Pro includes developer documentation, but code-level changes should only be added for a specific need. For most stores, it is safer to begin with interface settings, carrier aliases, correct email templates, and diagnostic logs. A snippet only makes sense when you need to change behavior that is documented and you have a clear rollback path.

For example, the documentation mentions developer-level control over the Mark as Shipped checkbox behavior. But without verifying the current plugin version and a proper test environment, you should not drop PHP into a live site. If managers frequently close orders as shipped by accident, first try fixing the process: quantity checks, partial shipment status, and visual status colors. Leave code for cases where the behavior problem is recurring and confirmed in testing.

What You Can Improve Without Code

• Create a separate warehouse instruction that explains which carrier to choose, when to use Partially Shipped, and what to write in the shipping note.
• Align carrier alias names with the CSV or API source and keep the mapping table next to the import procedure.
• Use a test order before every email template change.
• Enable logs only during troubleshooting so you do not keep extra technical data longer than necessary.
• Re-check the email customizer after WooCommerce updates or after changing the email template.

How to Tell the Setup Is Working

Result validation should cover the full chain, not just the admin area. If the manager sees the tracking number in the order, that does not automatically mean the customer received a clear email, the link opens the carrier page, PayPal sync completed successfully, or the CSV did not create duplicates. For Advanced Shipment Tracking Pro, a good validation looks like a mini-audit of one test order.

Validation Chain

1. The order shows the carrier, tracking number, ship date, and the source of the entry if that is displayed.
2. The order status changed exactly as intended: a partial shipment did not become a full one.
3. The customer email includes the tracking widget and does not duplicate an older email from another plugin.
4. The customer account shows the tracking link.
5. The carrier link opens and inserts the tracking number correctly.
6. If PayPal or Stripe sync is enabled, the order contains a note or column confirming that the data was sent.
7. If CSV or API was used, the logs show no duplicate, invalid carrier, or authentication failed errors.

After this check, you can move on to a bulk batch. If even one link in the chain is broken, fix it before launching the import. A bulk CSV with the wrong carrier alias will not create one issue - it will create dozens or hundreds of identical errors.

Common Problems and Troubleshooting

Shipment tracking issues rarely appear as one big obvious error. More often, the plugin works, but the data does not appear where the customer or manager expects it. Below are scenarios that are especially typical for WooCommerce tracking, carrier mapping, CSV or API flows, and the email workflow.

The Carrier Does Not Appear When Adding Tracking

Symptom: the manager opens the add tracking info form, but the required carrier is missing from the list. Cause: the carrier is not enabled in Shipping Carriers, the carrier database is outdated, or the shipping service needs to be added as a custom carrier. What to check: the active carrier list, country search, and whether Sync Carriers is needed. How to fix it: enable the carrier, add a custom carrier with the correct tracking URL, or update the database. Roll back a carrier database reset if it removes the custom entries your current process depends on.

CSV Import Shows Invalid Carrier

Symptom: CSV rows do not import even though the order ID and tracking number look correct. Cause: the tracking_provider value in the file does not match an enabled carrier or alias. What to check: the exact spelling from the CSV, the Custom API Name field, extra spaces, and letter case. How to fix it: add the alias in the carrier record or normalize the file to the standard carrier name. For a large batch, always import 2-3 rows first.

The Customer Does Not See Tracking in the Email

Symptom: tracking info exists in the order, but the email goes out without the widget. Cause: email display is not enabled for the required status, another template sends the email, the status transition is wrong, or the tracking number was added after the standard email was already sent. What to check: Order Emails Display, the specific status settings behind the gear icon, the email customizer, and any conflict with an email template customizer. How to fix it: enable the widget only in the correct email, send a test, and disable the duplicate notification channel.

Partial Shipment Closes the Entire Order

Symptom: the first package has shipped, but the order looks fully shipped. Cause: the manager marked all items, the CSV sent status_shipped as a full shipment, or auto-complete logic is enabled during import. What to check: quantity by SKU, status_shipped, the API or CSV auto-complete setting, and multiple tracking per item. How to fix it: repeat the test with correct qty values, and disable the questionable automation until the file or API mapping is corrected.

The API Returns an Authorization or Access Error

Symptom: the external service does not add tracking, and the API responds with an authorization or access error. Cause: an invalid Consumer Key or Secret, insufficient user permissions, an incorrect endpoint, or a security block on the site. What to check: WooCommerce REST API keys, Read/Write permissions, the endpoint URL, the WooCommerce log, and any security plugin. How to fix it: create a new key with the minimum required permissions, test one POST request in a staging environment, and delete old test keys afterward.

Tracking Numbers Are Duplicated

Symptom: multiple identical tracking numbers appear in the order. Cause: a repeated CSV or API request, disabled duplicate tracking protection, or incorrect use of replace_tracking. What to check: the Restrict adding the same tracking number setting, the external system's behavior during retries, and the API log. How to fix it: enable duplicate protection, configure the external system for idempotent submission, and manually remove incorrect entries only after checking the emails.

PayPal or Stripe Sync Is Not Confirmed

Symptom: the tracking number is added in WooCommerce, but the payment transaction does not show the expected information. Cause: sync is not enabled for the required payment method, API keys are incorrect, the order did not move into the status that triggers data transfer, or the error is recorded in the logs. What to check: the PayPal or Stripe Tracking panel settings, sandbox mode, payment methods, order notes, and WooCommerce - Status - Logs. How to fix it: start with test mode and one order, then move to live mode. If the error repeats, temporarily disable sync so the team does not assume the data was sent when it was not.

When Advanced Shipment Tracking Pro Is the Right Choice

Advanced Shipment Tracking Pro is worth using if your WooCommerce store already deals with manual copying of tracking numbers, customer shipping questions, partial shipments, warehouse CSV files, shipping service integrations, or the need to pass tracking data to PayPal and Stripe. The plugin is especially strong when you need more than just "a link" and want a full post-purchase workflow: order, carrier, tracking number, status, email, customer account, bulk import, and troubleshooting.

Before rolling it out, do not try to enable every feature in one evening. Start with carriers, statuses, and a test order. Then configure the email widget, verify partial shipment behavior, add CSV or API, and only after that enable payment synchronization or scheduled FTP/SFTP import. That sequence lowers the risk of duplicates, incorrect emails, and carrier mapping errors.

If, after testing, you determine that the store really needs this kind of shipment management layer, you can download Advanced Shipment Tracking Pro and test it on a backup or staging site. The best measure of a successful setup is simple: the manager adds the tracking number once, the customer sees it without contacting support, and the team can quickly prove where and when the shipment number was entered.