A lot of Shopify and Amazon FBA sellers start the same way. A reorder gets placed in a spreadsheet, price updates happen in email, carton details sit in WhatsApp, and the final version of the order lives in nobody's head with complete accuracy. That works until a factory ships the wrong variant, a freight quote changes, or duties hit harder than expected and the margin on a “best seller” suddenly looks thin.
That's why creating a purchase order matters. For an inventory-based e-commerce brand, a PO isn't admin. It's the document that locks the commercial deal, the logistics plan, and the financial assumptions into one record. It becomes the reference point from order placement through receiving, invoice matching, and payment reconciliation, as outlined in Wikipedia's overview of purchase orders.
For sellers importing products, the difference between a basic PO and a disciplined one usually comes down to one thing. The strong PO includes landed cost thinking before the order is sent, not after inventory arrives.
Table of Contents
- Why Spreadsheets and Emails Can't Manage Your Purchase Orders
- The Anatomy of a Perfect E-commerce Purchase Order
- Beyond Unit Price Calculating Landed Cost at the PO Stage
- Negotiating Terms and Communicating Like a Pro
- Your PO Workflow Approval, Version Control, and Common Mistakes
- How Supply Chain Software Ends PO Chaos
Why Spreadsheets and Emails Can't Manage Your Purchase Orders
The common assumption is that a spreadsheet is fine until the business gets bigger. That's usually wrong. The system starts breaking long before the revenue line says “mature company.”
A seller sourcing from China for Shopify and FBA might have one sheet for order quantities, one email chain for price negotiation, a separate message thread for packaging changes, and a freight forwarder quote that never gets reflected back into the PO. The result isn't just messy documentation. It's weak cost control.
A 2025 Shopify survey of 1,200 DTC sellers found that 68% cite inaccurate landed costs as their top profitability killer, while 42% still use spreadsheets for POs that overlook duties and freight volatility, leading to 15-20% margin erosion. That is the primary issue with manual PO handling. It hides true inventory cost until it's too late to fix.
The manual process fails in predictable ways
When teams rely on Excel, Gmail, and WhatsApp, the same issues appear again and again:
- Version confusion: The supplier is quoting one unit price, while the buyer approved another version in a different thread.
- Spec drift: A color, insert, carton mark, or packaging detail gets discussed but never lands in the final document.
- Freight blindness: The PO reflects factory cost only, while the brand's actual cash exposure includes freight, duties, insurance, and prep fees.
- Receiving disputes: The warehouse or prep center gets inventory with no clean reference document to check against.
Practical rule: If a seller can't answer “which exact version did the supplier accept?” within a minute, the PO process isn't under control.
That's why sellers eventually outgrow spreadsheets even when order volume still feels manageable. The issue isn't complexity for its own sake. It's that inventory businesses need one approved source of truth.
A good way to see the gap is to compare landed cost spreadsheets vs software for inventory purchasing. The spreadsheet can list numbers. It usually can't keep approvals, revisions, supplier acknowledgments, and logistics assumptions aligned in one place.
A PO should protect margin, not just record intent
For inventory brands, creating a purchase order should do three jobs at once:
JobWhat it means in practice
Commercial control
Lock the agreed SKU, quantity, price, and payment terms
Operational control
Give the supplier and receiving team one exact reference
Margin control
Reflect the cost assumptions behind the buy decision
Without that structure, the PO becomes a weak summary of a conversation. With it, the PO becomes the operating document for the entire order.
The Anatomy of a Perfect E-commerce Purchase Order
A good PO should survive first contact with reality. The supplier should be able to start production from it. The forwarder should be able to book against it. Your 3PL or prep center should be able to receive against it without asking what was ordered.
Basic templates usually cover the obvious fields: PO number, buyer and supplier details, item descriptions, quantities, prices, addresses, dates, and payment terms. For inventory-based e-commerce, that is only the starting point. A PO also has to protect against the mistakes that show up weeks later, such as the wrong barcode on a carton, the wrong destination on the shipping docs, or a supplier producing an older version of a bundle.
The fields that must be on every PO
These fields belong on every PO. The difference between a weak PO and a usable one is how precisely each field is written.
- PO number: Use a unique, searchable format such as
PO-2026-0147. Keep one sequence across the business or a clear supplier-based logic. Reused numbers create accounting and receiving problems fast. - Buyer details: Include the legal entity name, billing address, and the actual operating contact for questions. If your trading entity differs from your brand name, show the legal entity.
- Supplier details: List the factory or vendor legal name, primary contact, factory address, and internal payee reference if your finance team needs it.
- Ship-to details: Name the exact destination. For Shopify and FBA brands, that might be a 3PL, prep center, freight consolidator, or your own warehouse. “To be confirmed” is how cartons end up routed wrong.
- Line items: Each line should include internal SKU, variant details, product description, unit of measure, quantity, and agreed unit price.
- Dates: Separate production completion date from ex-factory ship date or requested delivery window. Those are different commitments.
- Payment terms: Spell out deposit percentage, balance trigger, payment method, and whether the balance is due before shipment, against inspection, or against copy docs.
What e-commerce sellers should add beyond the basics
Many first-time founders under-specify the order at this stage. Office purchasing templates are built for buying standard items. Imported inventory is different because small ambiguities turn into expensive corrections.
Add these fields if you buy private label or custom product:
- Product identifiers that match how you sell: Include your internal SKU and the supplier SKU if they are different. If you sell apparel, bundles, or multipacks, break out size, color, and pack configuration on the PO itself.
- Packaging and compliance instructions: State carton pack, inner pack if relevant, FNSKU or UPC labeling, barcode placement, suffocation warning requirements, insert rules, and any retailer or marketplace packaging requirements.
- Destination type and routing notes: State whether the goods are shipping direct to FBA prep, direct to your warehouse, or to a consolidation point. This matters for labeling, pallet specs, and booking.
- Incoterms: Write the agreed term on the PO. If the commercial agreement is FOB Ningbo, the document should say FOB Ningbo. Do not leave shipping terms buried in email.
- Approved reference files: Cite the final spec sheet, artwork version, dieline, or sample approval reference. If revision control is weak, suppliers will often produce against the last file they have, not the file you intended.
- Lead time commitment: Record the agreed production timeline in calendar days or by a named completion date.
One missing line can create a full rework cycle.
I have seen a supplier hit the right quantity, right unit price, and right carton count, then still miss the order because the PO never stated which barcode version applied to that SKU. The factory used the previous print file. The goods were technically finished, but they were not ready for Amazon check-in. The fix was relabeling, extra prep fees, and a delayed launch.
For founders setting up a first formal template, purchase order templates for product-based businesses can save time. Use the template as a starting point, then add the fields your business needs to receive, inspect, and reconcile orders without guesswork.
A useful mental model
A reliable e-commerce PO answers three operational questions before it is sent:
- Can the supplier build the exact SKU and packaging configuration from this document alone?
- Can the receiving team check cartons, labels, and quantities against this document without hunting through email?
- Can finance match the invoice and payment terms against this document without reopening the commercial agreement?
If any answer is no, the PO is still a draft.
Beyond Unit Price Calculating Landed Cost at the PO Stage
A founder approves a reorder at $4.80 per unit, confident the margin still works. Two weeks later, the forwarder updates the freight quote, customs asks for the correct classification, and Amazon prep adds another layer of cost. The PO was technically correct. The buy decision was not.
That is the gap basic PO advice misses. For inventory-based e-commerce, especially Shopify and Amazon FBA, the right time to estimate landed cost is before the PO goes out. Once the order is in production, you can still update forecasts, but you cannot undo a buy that never had the margin to begin with.
What landed cost means on a live PO
At the PO stage, landed cost is a working SKU-level estimate of what each sellable unit will cost by the time it is ready to receive, prep, and sell. It usually includes:
- Product cost: Factory unit price multiplied by quantity
- Freight cost: Ocean, air, or courier cost allocated down to the SKU
- Duties and import taxes: Based on HS code, customs value, and country of origin
- Insurance and customs-related fees: Cargo insurance, broker fees, filing fees, port charges
- Post-arrival handling: FBA prep, labeling, palletization, drayage, warehouse intake, or carton forwarding when those costs belong in inventory economics
The point is not perfect precision. The point is making the buying decision with a realistic cost range instead of a factory quote alone.
A lot of smaller brands calculate landed cost after the shipment lands because finance needs it for reporting. Purchasing needs it earlier. If SKU A only works at a 31% gross margin after freight and duty, and your target is 40%, that should stop the PO or force a change in quantity, terms, packaging, or channel plan.
A practical FBA example
Say you are reordering 3,000 units of a kitchen accessory for Amazon FBA.
The supplier offers a lower unit price if you increase the order from 2,000 to 3,000 units. On paper, that looks like a win. In practice, the larger order may push you into a different freight profile, increase storage exposure, and change how much cash is tied up before sell-through. If the SKU also needs polybagging, suffocation warnings, and FNSKU labeling, the cheapest factory quote may produce the weaker landed margin.
That is why I review landed cost in this order:
StageWhat the buyer should confirm before issuing
SKU setup
Correct SKU, product description, pack-out, HS code, country of origin
Cost review
Unit cost plus expected freight, duty, insurance, prep, and receiving costs
Margin check
Whether the SKU still works after marketplace fees, discounting, and target gross margin
Cash check
Deposit, balance payment timing, freight timing, and how much cash the reorder locks up
PO issue
Send only after the assumptions behind the buy are documented
A practical walkthrough of how to calculate landed cost for imported products helps founders build this into reorder planning instead of treating it as cleanup after the shipment arrives.
This video gives a useful overview before teams formalize their own process.
Margin rule: If the landed cost is not visible at the SKU level before approval, the PO is only half finished.
What often gets missed
The expensive mistakes are usually small:
- The HS code is copied from an old item and the duty assumption is wrong
- The freight estimate is stale and no one updated it for the current season or shipment mode
- Packaging changed and the new carton dimensions raised freight cost per unit
- Prep requirements were discussed in email but never priced into the order
- The order mixes SKUs with very different cube or duty profiles but cost is averaged too loosely across the whole PO
Each one sounds manageable. Together, they can turn a healthy reorder into inventory you are pushing through discounts just to get cash back out.
Creating a purchase order properly means pressure-testing the landed assumptions before production starts. That is how a PO becomes a real buying control for e-commerce inventory, not just a document with quantities and prices.
Negotiating Terms and Communicating Like a Pro
A perfect PO document can still fail if the communication around it is vague. In e-commerce, that usually shows up a few weeks later as a preventable cost problem: the factory used the old insert, carton specs changed without anyone pricing the freight impact, or a supplier treated an estimate as approval. By the time the shipment is on the water, the margin loss is already locked in.
That is why I treat supplier communication as part of PO control, not admin. Spendflo's guide to creating purchase orders explains that the PO process includes issuance and supplier confirmation, and that the PO later supports three-way matching against the goods receipt and invoice. If the terms are fuzzy at the negotiation stage, the confusion follows the order through production, receiving, and payment.
What good supplier communication looks like
Good communication points every decision back to one version of the PO. It also forces the supplier to confirm the details that usually cause expensive surprises for Shopify and FBA brands: packaging specs, prep requirements, delivery window, and any change that affects landed cost per SKU.
A common but risky message looks like this:
Please proceed with the reorder. Same as last time. Need it soon. Let us know if price changed.
That message creates too much room for interpretation. "Same as last time" can mean the wrong packaging file, an old carton pack, outdated labeling requirements, or a price that no longer reflects current material cost. For an FBA shipment, even a small misunderstanding on prep or carton labeling can add fees, delay check-in, or force a last-minute 3PL fix.
A clearer, safer alternative looks like this:
Please confirm acceptance of PO-2026-0147. This order includes SKU A in black and SKU B in sand. Unit prices, quantity split, packaging requirements, and delivery window are listed in the PO. Please confirm price, lead time, carton specs, and any exceptions before production starts.
That last sentence matters. Carton specs are not a side detail if freight is allocated at the SKU level. If a factory changes pack-out and the cartons get larger, the landed cost you approved earlier is already wrong.
Terms worth negotiating before approval
Founders do not always get strong terms on the first few orders. New brands usually have less bargaining power, especially with overseas suppliers that prefer their own template and payment schedule. Even so, a handful of terms are worth pushing on early because they affect cash flow, lead time risk, and landed margin.
- MOQ flexibility: A supplier may hold the line on total units but allow a better size, color, or bundle mix within that MOQ.
- Payment structure: Deposit percentage, balance timing, and the trigger for final payment should be written in the PO and confirmed in the acceptance.
- Lead time commitment: "About 30 days" is weak. Ask for a production completion window and a date for cargo readiness.
- Packaging and prep responsibility: Spell out who handles FNSKU labels, suffocation warnings, inserts, carton markings, pallet rules, and any retailer-specific compliance work.
- Change control: Require written confirmation against the PO for any change in quantity, price, packaging, ship date, or shipping term.
I also recommend including one additional requirement that standard purchase order guides frequently overlook. Request that the supplier verify any factor that might impact landed costs before you authorize production. This encompasses carton dimensions, gross weight, inner pack quantity, and preparation requirements. If these specifications change after your approval, the unit cost on the PO may remain constant while the actual margin decreases.
Supplier selection affects how painful these conversations become. A practical supplier evaluation matrix for product brands helps compare factories on responsiveness, documentation discipline, quality consistency, and willingness to confirm changes in writing.
A clearer way to handle PO changes
PO changes are where teams lose control fastest. One message in email, another in WhatsApp, a revised artwork file in Drive, then a production update that reflects only half the request.
A risky change request sounds like this:
Can we update the order to the newer packaging? Also maybe adjust quantities if possible.
That request leaves open questions the buyer should close before the supplier acts. Which packaging version is approved. What quantity mix should change. Does the update affect unit price, carton count, or production timing. For imported inventory, each one can change landed cost.
A safer version sounds like this:
Please revise PO-2026-0147 to use packaging file version B. Keep total units unchanged. Update the quantity mix as listed in the attached revision note, with SKU A increased and SKU B decreased. Please confirm any impact on unit price, carton count, gross weight, production timing, and booking readiness before proceeding.
That is the standard to aim for. Specific, traceable, and tied to the PO version everyone is working from.
Your PO Workflow Approval, Version Control, and Common Mistakes
A founder approves a reorder on their phone while traveling. The supplier starts production from an older attachment. Finance budgets off the newer quantity. The forwarder books space against carton counts from neither version. That is how a routine PO turns into margin leakage.
For inventory brands selling on Shopify or Amazon FBA, approval discipline matters because PO mistakes do not stay on paper. A quantity change can alter prep fees, carton counts, duty exposure, and the landed cost by SKU you expected to hit. If that change is approved casually, the margin model you used to greenlight the buy is already out of date.
A practical workflow for small e-commerce teams
A usable workflow does not need procurement software language. It needs one owner, one approved version, and one clear record of what the supplier accepted.
- Draft the PO
Enter SKU, item description, quantity, unit price, Incoterm, ship-to location, payment terms, packaging version, labeling requirements, and target ship window. - Review the economics
Check the order against open-to-buy, stock coverage, and expected SKU-level landed cost. This is the point to catch a low-margin SKU before cash is committed. - Approve the issue version
The approver signs off on the exact document being sent. If the founder is the approver, record it in writing inside the PO thread or file history. - Send one controlled version to the supplier
Send the PO PDF or system-generated document with the PO number and version in the filename. Do not mix instructions across email, chat, and voice notes. - Get written supplier acknowledgment
The supplier should confirm quantities, pricing, specs, dates, and any exceptions. No acknowledgment, no assumption that production is aligned. - Tie follow-up documents back to the PO
Deposit slip, proforma invoice, packaging signoff, booking form, and final invoice should all reference the same PO number and current version.
One rule saves a lot of cleanup later. If the commercial terms or execution details change, the PO changes too.
Common mistakes that create expensive surprises
These are the failures I see most often with newer brands buying from overseas factories.
- Treating silence as approval
A supplier may start from an old quote, an old spec, or whatever message was easiest to find. Written acknowledgment closes that gap. - Approving without checking landed cost again
Buyers often review unit price and stop there. If the revised quantity mix changes carton efficiency or pushes one SKU into a different duty or prep profile, margin can slip before the order is placed. - Using vague item descriptions
“Black yoga mat” does not tell a factory enough. Material, dimensions, thickness, insert, barcode placement, polybag warning, carton pack, and packaging version often matter more than the color. - Letting revisions live in chat
If WhatsApp says one thing and the PO says another, the supplier has cover to follow either one. - Keeping disconnected paperwork
Matching becomes slow when invoices and shipping documents are stored separately from the order. Keeping supplier invoices organized by purchase order makes receiving and payment review much easier. - Verbal approval with no record
Founders do this all the time. It works until there is a price variance, a short shipment, or a cash question from finance.
A lightweight version control standard
Small brands do not need a complicated policy. They need a rule everyone follows every time.
SituationVersion action
Typo fix only
Keep version if there is no commercial or operational change
Quantity change
New version
Price change
New version
Delivery date change
New version
Packaging or labeling change
New version
Use a simple naming format such as PO-2026-0147-v2. Mark the old version as superseded. Resend the full document, not just the changed line. Then get the supplier to confirm they are producing against that exact version.
That last step matters. If your team is calculating margin on v3 and the factory is building v1, the problem is no longer administrative. It is inventory risk, cash risk, and margin risk on every unit in the container.
How Supply Chain Software Ends PO Chaos
Manual PO management creates the same pattern over and over. The spreadsheet holds quantities. Email holds approvals. WhatsApp holds clarifications. A drive folder holds invoices. Nobody sees the whole order in one place.
That setup breaks down fastest for brands with overseas suppliers, multiple SKUs, and channel-specific handling requirements. The founder needs landed cost clarity before committing cash. Operations needs one approved document. Finance needs a clean path to matching and payment. Suppliers need one version to execute against.
Software fixes that by replacing scattered communication with a single operating record. The PO becomes the center of the workflow, not a file attachment. Messages sit next to the order. Revisions are visible. Production checkpoints can be tracked against the same thread. Receiving and invoice review happen against the same reference.
The biggest upgrade is usually financial visibility. When the system ties product cost, freight assumptions, duties, and related fees into the buying workflow, the team can evaluate margin before issuing the order instead of discovering problems later. For Amazon FBA sellers, that matters because prep and fulfillment economics leave less room for sloppy purchasing. For Shopify brands, it matters because inventory cash gets tied up early and often.
A dedicated platform also changes behavior. Teams stop saying “latest attached” and start working from one current version. Suppliers stop hunting through message chains. Approvals stop depending on memory. That's what professionalizing creating a purchase order really looks like. Not more bureaucracy. Better control.
Brands that have outgrown spreadsheets, inboxes, and supplier chat chaos can see how Supply Automate centralizes purchase orders, supplier messaging, version control, production tracking, and SKU-level landed cost in one workspace. It's built for Shopify and Amazon sellers who need cleaner buying decisions before the order is sent, not after the margin is gone.