A supplier who passed onboarding can deteriorate slowly. Stock files arrive later. A new warehouse begins handling orders. A packaging change causes more damage. A higher charge appears in small increments. None of these may look serious on a single order, but together they can erase margin and weaken the buyer promise.
Review the supplier through completed orders and customer outcomes, not only the invoice or a monthly vendor score. Keep the original requirements visible, measure exceptions, and define what action follows a missed threshold. A review is useful when it changes a listing, process, volume allocation, or supplier decision.
This is the final part of the Dropship Supplier Guide. The earlier steps established requirements, identity and product evidence, terms and margin, pilot results, and written agreements and backup options. Now those commitments need a feedback loop.
Build an order ledger both sides can reconcile
Give each customer order a stable internal ID and store the supplier’s order ID, SKU, variant, warehouse, ship-to region, promised ship date, accepted time, label time, first carrier scan, delivery event, supplier charge, refund, replacement, and final case outcome. Keep a snapshot of the buyer-facing offer at purchase. If the supplier changes a product page or rate sheet later, the snapshot shows what the customer was actually promised.
Reconcile the ledger with supplier invoices and carrier events at least weekly during a new relationship. A supplier’s portal may mark an order “fulfilled” at label creation, while the carrier has no parcel. An order may appear delivered but have a wrong-item complaint. Keep these states distinct instead of using one convenient completion flag.
Record reasons for exceptions using a small, consistent set: unavailable stock, wrong variant, supplier processing delay, carrier delay, damage, defect, address problem, buyer remorse, or unknown. Allow notes for unusual cases. If every problem is coded “other,” the report cannot guide a fix. If the store made a mapping or address error, attribute it honestly rather than assigning every failure to the supplier.
Limit access to customer details. The supplier performance report usually needs order IDs, regions, SKUs, and timing, not full names and addresses. The FTC’s vendor-security guidance supports limiting a vendor’s access to the data required for its work.
Measure the parts of service that affect buyers
Use a few definitions that can be calculated from raw orders. Stock acceptance rate is accepted orders divided by orders submitted while supplier data said the item was available. On-time carrier handoff is orders with a first carrier scan by the internal deadline divided by accepted orders due in the period. Correct-item rate counts orders without a verified variant or quantity mistake. Tracking completeness counts orders with a usable carrier and tracking ID.
Add buyer outcomes: delivered-within-promise rate, defect and damage rate, support contacts per order, refund rate, and time to remedy. Keep the denominator and time window visible. A supplier can claim 99% “on time” by excluding cancellations or measuring from a later internal acceptance time. Your score should reflect the promise your store made when the buyer placed the order.
Compare by SKU, warehouse, route, and season before making a broad judgment. One warehouse may have a handoff problem while another performs well. A fragile item may cause most damage claims. A holiday peak may change carrier performance. Segmentation identifies a fix; a single aggregate number may hide it.
Do not treat a tiny sample as a precise rate. One defect in ten orders is a warning, but it does not establish a stable 10% long-run defect rate. Combine the count with the severity and cause. A single wrong-child-safety label may require immediate pause; several minor cosmetic complaints may call for inspection and a revised listing. Record confidence and act in proportion to the risk.
Recalculate realized contribution
Supplier charges are only part of the financial result. For each order or cohort, calculate customer payment less supplier product and fulfillment cost, platform and payment fees, acquisition, support, refunds, replacements, and unrecovered return cost. The Shipping Profit worksheet provides an order-level structure. Use consistent tax treatment and separate collected tax from money the business can spend.
Compare expected and actual cost by supplier, SKU, and shipping zone. Investigate surcharges, package-size changes, duplicate labels, currency shifts, and missing credits. A $1 increase across hundreds of orders may matter more than one dramatic exception. Ask whether a cost change reflects a new rate sheet, a changed package, or an invoice error before changing customer prices.
Revisit margin after delivery and the return window. A campaign can produce positive contribution at checkout and negative realized contribution after refunds. The Merchant Center conversion-quality guide explains how traffic metrics connect to retained orders. Supplier review should feed that decision: do not increase advertising for a product whose fulfillment outcome is deteriorating.
Use a downside case for volume plans. If demand doubles, can the supplier maintain stock and handoff speed? If returns rise during a new batch, can the store fund refunds before supplier credits arrive? A profitable small pilot does not prove unlimited capacity.
Create alerts before the buyer deadline
Daily exception review should focus on orders that can still be saved. Flag orders with no acceptance, a rejected SKU, a missing first carrier scan near the promised date, or a tracking number that has not moved. Route each flag to an owner who can contact the supplier and update the buyer when needed.
The FTC shipment rule guide explains seller duties when promised shipment is delayed. Your alert must fire early enough to determine whether the promise can still be met and, if not, handle the buyer’s required choices. Waiting for a monthly vendor meeting is too late for an individual order.
Set a separate urgent path for product safety or material misdescription. If a supplier changes a component without notice or a product is recalled, pause the affected listing, identify open and completed orders, preserve evidence, and follow the applicable remedy. Check the CPSC recall database for relevant products and keep contact records sufficient to reach affected buyers.
Hold a useful supplier review
Use a weekly operational review during a pilot or unstable period and a monthly review once the process is predictable. Send the supplier a shared case list in advance. The meeting should resolve discrepancies in data, assign owners, and set dates for corrective action. “Improve shipping” is not a plan; “restore first carrier scan within the agreed window for warehouse B, show the next 20 orders, and review on Friday” can be tested.
Use a compact scorecard:
| Area | Evidence | Possible response |
|---|---|---|
| Stock | Rejected orders despite available status | Buffer, faster feed, or pause SKU |
| Handoff | First carrier scan versus promise | Warehouse correction or revised promise |
| Product | Variant errors, defects, changed components | Inspection, new sample, or stop sale |
| Economics | Invoice variance, surcharges, missing credits | Reconcile, renegotiate, or reprice |
| Exceptions | Time to buyer remedy and supplier credit | Escalate, change workflow, or reduce volume |
| Data | Missing status, late feed, access incident | Fix integration or limit access |
Save the supplier’s response and the next measurement date. When a corrective action is complete, retest the same scenario that failed. Do not declare success because a meeting was cordial or a new policy document was sent.
Choose a response level before a crisis
Define four actions. Continue when performance meets the promise and margin target. Improve when a contained issue has an owner and retest date. Reduce when repeated misses warrant lowering volume, pausing affected SKUs, or limiting regions. Exit when critical safety, identity, product, or fulfillment issues remain unresolved or the economics no longer work.
Tie each action to observable thresholds. A small store may use counts as well as percentages: two wrong-variant shipments in the first ten orders may trigger a pause, while a mature operation can use a rolling rate. Choose thresholds based on product severity and customer impact, not a borrowed industry benchmark. The written supplier agreement and backup plan should explain how orders already accepted are handled during a pause or exit.
When moving volume, verify the backup’s current stock, price, product facts, shipping route, and customer policy before switching. Do not quietly substitute a different item for an open order. Customers should receive a truthful choice if the original offer cannot be met. Keep the old supplier’s outstanding returns and credits on a separate closeout list so ending new orders does not erase existing obligations.
Review the product and the supplier together
Poor performance can have several causes. A supplier may be reliable while the store’s listing promises a delivery window that no available service can meet. A high return rate may reflect a misleading size chart rather than a manufacturing defect. A costly route may be unprofitable even with excellent fulfillment. Use the order ledger to separate product, listing, channel, carrier, and supplier causes.
Update the original supplier brief after each meaningful lesson. If a new quality check or data field would have prevented a recurring issue, make it a requirement for future candidates. If the product itself cannot produce a good buyer experience at a viable price, stop selling it rather than endlessly changing vendors. The purpose of supplier management is a customer offer the store can keep, repeatedly and profitably.