Profit & Finances

A purchase order is two objects

Tracking supplier payment schedules alongside product margins — and the number that decides which supplier is actually cheaper.

AmazeBase 13 min read Suppliers & Cash Flow

One purchase order splitting into two paths: the goods, and the dated payments

Most sellers keep supplier management in two places that never meet: a margin spreadsheet, and a folder of invoices with dates on them.

Podcast episode 20 minutes 57 seconds

This audio is AI-generated with NotebookLM from this article.

That split feels natural. Profitability is an analysis question; paying the factory is an admin task. They sit with different tools and often different people.

It's also the reason profitable Amazon businesses run out of money.

Because a purchase order isn't one thing. It's an inventory commitment and a cash schedule wearing the same document. The inventory half determines what you'll earn. The cash half determines whether you can get there. Look at either alone and you'll make a decision that's correct in one dimension and ruinous in the other.

Here's how to hold both at once — and a number that settles the argument sellers have most often, which is which supplier is cheaper.

01Two objects, one document

Split every PO deliberately, because the two halves have different owners, different questions, and different failure modes.

  • The inventory commitment — units, landed cost, when they become sellable, what they'll contribute. Feeds product economics and reorder planning.
  • The cash schedule — a set of dated obligations, each with an amount and a trigger. Feeds the cash timeline.

They share exactly two facts: the unit cost and the arrival date. Everything else diverges. And those two shared facts are precisely where systems drift apart, so they're worth guarding — §08 comes back to it.

The PO you can afford and the PO you should place are different documents until you put them on one screen.

02The quote is not the cost

A supplier quotes $8.00. That number belongs in a negotiation, not in a margin calculation.

Landed cost is everything required to turn a quote into a sellable unit: manufacturing, packaging, inspection, labelling, prep, inland transport, international freight, duty and tariffs, insurance, and whatever the last shipment taught you to expect.

The practical consequence shows up when comparing suppliers. A $7.50 quote against an $8.00 quote is not a saving until you've added:

  • MOQ — a lower price at 5,000 units when you need 2,000 is a worse deal, not a better one.
  • Incoterms — EXW and DDP quotes are not comparable numbers. One of them contains the freight.
  • Packaging and prep — who does it, and is it in the price?
  • Defect rate — 3% unsellable is 3% on your effective unit cost.
  • Payment shape — the subject of the next two sections.

Compare the economic cost of the inventory, not the number on the quote.

03Payment shape, and why it doesn't show up in margin

Two suppliers, identical landed cost, identical product.

  • Supplier A: 30% at order, 70% before shipment.
  • Supplier B: 20% at order, 80% thirty days after shipment.

Your product margin is byte-for-byte identical. Your business is not.

The reason is the shape of the gap between paying and being paid. An Amazon seller pays a factory, waits for production, waits for a boat, waits for check-in, sells over weeks, then waits again for Amazon's disbursement cycle. Cash leaves early and returns late, and the interval is measured in months.

Two numbers describe that gap. Almost nobody computes either:

cash conversion gap = days from the first supplier payment
                      to the first Amazon disbursement
                      from that inventory

peak exposure       = the largest amount you are out of pocket
                      at any point in the cycle

Margin tells you what a unit earns. These two tell you what it costs to wait for that, and how much of your business is tied up while you do.

04So which supplier is actually cheaper?

Now make the two suppliers differ on price as well, the way they do in reality — the cheaper one is slower and wants its money sooner.

Same product, 3,000 units, sells at $35

Cash back per unit after Amazon fees and ads
$12.00
Sales rate once sellable
50/day
Supplier A — landed cost
$6.80
Supplier A — terms · production · transit
30/70 · 45d · 30d
Supplier B — landed cost
$7.20
Supplier B — terms · production · transit
20/80 net 30 · 25d · 30d

A is 5.6% cheaper per unit. Every instinct says take it. Watch what the cash does.

Cash exposure through one order cycle

How far out of pocket you are, day by day, from first payment to full recovery.

Supplier A — $6.80, 30/70, 75d to sellable Supplier B — $7.20, 20/80 net 30, 55d to sellable
$0 −$5k −$10k −$15k −$20k A · −$20,400 balance due day 45 B · −$21,600 balance due day 55 B recovers · day 111 A recovers · day 129 day 0 30 60 90 120
B is out of pocket by slightly more at the bottom, for 34 fewer days. Peak exposure barely differs; the time spent at peak is what separates them.

Turn the cycle length into how many times a year the same money works:

Contribution per unit is $12.00 less landed cost. Turns per year is 365 ÷ cycle days.
Per yearSupplier ASupplier B
Contribution per unit$5.20$4.80
Cash cycle129 days111 days
Capital turns per year2.833.29
Capital deployed$20,400$21,600
Annual contribution$44,148$47,376

The cheaper supplier earns $3,200 less per year on the same capital — and that's before counting what its 20 extra days of lead time cost in safety stock and stockout risk.

Add a second product competing for the same cash and the gap widens, because the constraint isn't the price. It's how long each dollar is stuck.

The rule

Compare suppliers on contribution per dollar per year, not price per unit. Price is one input to it. Terms and lead time are the other two, and they usually matter more.

05Turning a PO into dated payments

A $21,000 purchase order is not a $21,000 cash event. It's a set of obligations, each with an amount and a rule for when it lands. Four triggers cover essentially every real contract:

  • At order — dated on the PO date. Known immediately.
  • At shipment — dated when the goods leave. Estimated until they do.
  • N days after shipment — the same anchor, plus a fixed offset.
  • On a fixed date — dated as agreed.

Two of those four hang off an event that hasn't happened yet, which produces the trap:

Never store a date you derived from an estimate

Store the trigger and the offset, and compute the date on read. If you store the computed date, then move the shipping estimate two weeks, every downstream due date silently keeps the old value — and nothing anywhere tells you the schedule is now fiction.

And when the anchor doesn't exist yet, say so. A payment showing "unanchored — awaiting shipment date" is honest. One quietly dated on the PO date instead looks like a fact and is a guess.

This is the difference between a schedule that ages well and one that quietly rots. It's the same discipline as the rest of the stack: keep the inputs, derive the outputs, and label what's derived.

06Committed, scheduled, due

"How much do I owe suppliers?" has three legitimate answers, and mixing them is how a comfortable-looking month turns into a scramble.

CommittedThe total value of open POs. What you've promised, regardless of when it lands.
ScheduledInstalments with a trigger and a date, not yet paid. What's coming, and when.
DueScheduled and inside your planning window — the next 7, 30 or 60 days.

Three products in production at once — $10,000, $15,000, $20,000 — is $45,000 committed. At 30% deposits it's $13,500 due now, which reads as comfortable. The remaining $31,500 arrives weeks later, and it arrives alongside the ad spend, the freight invoices, the software and the existing balances that were already scheduled.

Nothing went wrong. Three reasonable decisions simply landed in the same fortnight.

07The danger is overlap, not any single order

One PO almost never causes a cash problem. The problem is the calendar view nobody builds.

Per-supplier questions — when do I pay Supplier A? — are the wrong grain. The business doesn't experience suppliers one at a time; it experiences a week in which $18,400 leaves.

So the useful view is a forward window across everything:

Next 7 days     $18,400 due          2 instalments
Next 30 days    $47,200 scheduled    5 instalments + freight
Next 60 days    $91,500 committed    incl. 2 POs with no schedule yet

And the one exception check worth running automatically: is any payment due before the inventory it's paying for turns into Amazon cash? That's not a rule of thumb — it's a comparison of two dates you already have, and it's the specific shape of every inventory-driven cash squeeze.

A supplier dashboard that lists fifty POs has told you nothing. One that says "two payments land before the cash they depend on" has done the whole job.

08One cost, one owner

Back to the two facts the halves of a PO share. Here's how they come apart.

A supplier raises the price from $7.20 to $7.80. The new PO records $7.80 correctly. The margin model still holds $7.20, because it was populated separately — or because it recalculates from a cached figure that nothing told to refresh.

Nobody made a mistake. There was simply no path from the purchase order to the profitability number, and the business now looks 8% more profitable than it is on every screen that matters.

The rule is structural, not procedural:

  • The PO is the source of truth for unit cost. Margin reads from it; it never holds its own copy.
  • A cost change recomputes what depends on it, automatically. If recomputation is a button someone has to remember, every number downstream is stale by default.
  • Estimates are labelled as estimates. Freight projected, duty assumed, a quote that expires in 30 days — mark all three, so a margin built on them declares itself.
  • A real invoice replaces its estimate, rather than being added beside it. Otherwise freight gets counted twice, once as a guess and once as a bill.

Chain it: supplier → PO → cost → product → margin. Every link is a read, not a copy.

09The supplier scorecard you already have the data for

Most supplier records are contact cards — a name, an email, a WhatsApp number. That's an address book, not a supply chain.

The useful record is a history, and almost every field in it is a by-product of orders you already ran:

  • Price history per SKU, with dates. Answers "has this crept up?" without opening old emails.
  • Payment terms, so a new PO inherits them instead of being re-typed.
  • Promised vs actual production time — quoted 25 days, averaged 34 across the last six orders.
  • Promised vs actual arrival, which is the number your safety stock should be sized from.
  • Estimated vs actual landed cost, so freight assumptions get better.
  • Defect and rejection rate, which is a silent addition to unit cost.
  • MOQ, currency, incoterms, so quotes are comparable at a glance.

The consistent-25-quoted-34-actual finding is the one that pays for the whole exercise. It shifts every reorder date for that supplier by nine days — and nine days is the difference between a comfortable restock and an airfreight decision.

You are not collecting supplier data. You are keeping the receipts from experiments you already ran.

10The one that ambushes importers

If you pay a factory in USD, freight in EUR and duty in your home currency, a landed cost that sums the raw amounts is wrong by however much the market moved.

Three rules keep it honest:

  • Store the currency and the rate on every payment, alongside the converted amount. Not a global setting — a property of the transaction.
  • Convert at the rate on the date the money moved, not today's rate. A deposit paid in March was paid at March's rate, permanently.
  • Scheduled future payments carry an assumed rate, and should be labelled as such — the amount is known in the supplier's currency, not in yours.

For a seller with meaningful FX exposure this quietly moves landed cost by several percent, which is enough to reorder a ranking of which products are worth restocking.

11Expected against actual

Every PO is a set of predictions that later resolve. Recording how they resolved is what makes the next PO better — and it's the cheapest thing on this list, because reality supplies the data for free.

Five predictions per order. Each closes on its own, and each improves a specific assumption for next time.
PredictedImproves
Production timeReorder timing
Arrival dateSafety stock
Landed costMargin accuracy
Payment dateCash forecast
Sell-through rateOrder quantity

Systematic error is a settings problem. Random error is the weather. You can't tell them apart without the record, and after five or six orders per supplier the pattern is unmistakable.

Which is the real answer to the accuracy question: the system doesn't get better at predicting. Your assumptions get better informed by your own history.

12Five numbers, together

For any product you'd consider reordering, these five belong on one screen. Separately they're reporting. Together they're a decision.

  • 01Contribution per unitWhat it earns after landed cost, Amazon fees and advertising.
  • 02Cover remainingUnits on hand and inbound, at current velocity, in days.
  • 03Order-by dateWhen the next PO must be placed, given measured lead time.
  • 04Cash required, and whenThe instalments that order creates, on their dates.
  • 05Cash recovery dateWhen the resulting inventory starts returning money.

Numbers 4 and 5 are the pair almost nobody has, and they're the ones that turn "should I reorder?" into a question with a real answer. The distance between them is your cash conversion gap. Everything in this article exists to make that distance visible before you commit to it.

Frequently asked

How do I track supplier payment schedules for an Amazon business?

Record each purchase order as a set of dated instalments rather than one total. Each instalment needs an amount, a trigger (at order, at shipment, N days after shipment, or a fixed date) and a paid/unpaid status. Store the trigger and offset rather than the computed date, so the schedule updates when your shipping estimate moves. Then view them across all POs on a forward calendar, not supplier by supplier.

Which supplier is cheaper — the lower price or the better terms?

Compare contribution per dollar per year rather than price per unit. A supplier that's 5% more expensive but 20 days faster and pays later can produce more annual contribution on the same capital, because the money completes more cycles. Price is one of three inputs; terms and lead time are the others.

What is cash conversion gap for an Amazon seller?

The number of days between your first supplier payment and the first Amazon disbursement from that inventory. It spans deposit, production, freight, check-in, the selling period and Amazon's payout cycle — typically 90 to 150 days. It's the single best measure of how much working capital a product needs.

Should I allocate freight to individual products?

Yes, for landed cost — freight is part of what a sellable unit costs. Allocate a shipment's freight across its SKUs by units or by volume, whichever matches how it was charged, and label it as an allocation. What you shouldn't do is allocate company overheads to units.

Why does my margin disagree with my purchase orders?

Almost always because the margin model holds its own copy of unit cost, or reads a cached figure nothing refreshed after the PO changed. The fix is structural: the PO is the source of truth, margin reads from it, and a cost change recomputes automatically rather than waiting for someone to press a button.

What should I track about a supplier beyond contact details?

Payment terms, MOQ, currency and incoterms so quotes are comparable; and the history your own orders generate — price per SKU over time, promised versus actual production days, promised versus actual arrival, estimated versus actual landed cost, and defect rate. The gap between quoted and actual lead time is usually the most valuable number in the record.

How far ahead should I forecast supplier payments?

At least one full cash conversion cycle — 90 to 150 days for most importers — because that's how long a decision you make today keeps affecting your balance. Shorter windows hide exactly the overlap that causes squeezes.

A purchase order is a financial decision

Supplier payments get filed as admin. They're the point where inventory, margin, lead time and cash all become the same decision — and the only place you can still change your mind cheaply.

What am I buying, what will it really cost, when do I pay, when does it arrive, how fast will it sell, what will it contribute, and what does all of that do to my cash. Those aren't seven questions. They're one, asked once, before you send the deposit.

Episode transcript

Read the full transcript

Transcribed automatically from the recording. Speakers are not labelled.

How can a profitable seller run out of cash?

[00:00]Imagine you're looking at your Amazon seller dashboard, right? And you are just moving a thousand units a week. Yeah, you feel like you're on top of the world. Exactly. Your spreadsheet says, um, you're making this beautiful 30% profit margin. By all the traditional metrics, you are absolutely crushing it.

Right. So why, when you check your bank account on some random Tuesday morning, do you suddenly not have enough cash to pay your freight forwarder? It is honestly the most terrifying disconnect in e-commerce. You know, you can have a business that looks incredibly healthy on a P&L, like paper profitable. Oh yeah, paper rich, cash poor. Exactly, but simultaneously, the business is just suffocating from a lack of cash. The money is everywhere except in your actual hand. Which brings us to our mission for this deep dive.

Why is a purchase order really two things?

We are going to decode a piece of, well, basically administrative paperwork that most people treat like a simple receipt. A very dangerous habit, yeah. Right, but it's actually the hidden engine dictating whether your business survives or goes bankrupt. We're looking at a pretty brilliant piece from AmazeBase titled, a purchase order is two objects. And the premise here is just a complete paradigm shift. Because I mean, most sellers view a purchase order, a PO as a single static document. You tell the factory what you want, they give you a total, you pay it.

Right, and eventually the goods arrive. But AmazeBase argues that if you really look closely, a PO is actually two entirely separate financial objects, and they're just wearing the disguise of a single document. Yeah. So half of that PO is an inventory commitment, and that determines what your product can potentially earn, right? But the other half is a cash schedule, and that determines if you can physically finance the wait to actually get paid. Yes, that is the crucial distinction. I actually like to think about it like evaluating a sports car.

[01:54]So the inventory commitment, that's the top speed. You're looking at the aerodynamics, the horsepower. Marvelling at how fast it can go, right? Exactly. But the cash schedule, that's the fuel tank. If you never bother to calculate how much gas it takes to reach the destination, it doesn't matter if your top speed is 200 miles an hour. Nope, you're gonna end up stranded on the side of the highway.

Literally stranded. That's a perfect visualization, honestly. Because if you only look at the top speed, you will make a decision that is correct in one dimension, but financially ruinous in the other. Wow. Yeah. And to truly grasp how this works, we have to start by dismantling the trap that catches almost everyone when they look at that first half of the document.

Why isn't the supplier's quote your real cost?

The inventory commitment part. Right. We have to fundamentally separate a supplier's quoted price from the true economic cost of the goods. Okay, let's unpack this. Because wait, what happens if my supplier gives me a quote that's just, you know, dirt cheap? Like an EXW quote. Yeah, they'll say I get an email factory offers to make my product for $8 a unit. Why is it so dangerous to just plug that $8 into my spreadsheet and boom, calculate my margins from there? Could I just calculate the freight later when I book the ship?

Because that $8 number is a negotiation starting point. It is not an economic reality. If you plug that into your margin model, you are creating phantom profitability. Like you said, an EXW or Ex Works agreement, that literally just means the factory will manufacture the product and leave it on their loading dock. So they just wash their hands of it right there? Exactly. You are responsible for every single expense after that moment. Which means paying to get it from their factory to the port, paying to load it onto a ship.

The ocean freight itself. Right, paying customs. And duty, and tariffs, and inland transport to the Amazon warehouse, oh, and insurance. Wow, okay. That adds up fast. It does. You cannot compare an Ex Works quote to say a DDP quote. Delivered duty paid. Right. Where the supplier actually handles the freight. Because they are representing entirely different bundles of services. What you actually need to calculate, what AmazeBase stresses, is the landed cost. The landed cost. Yeah. That encompasses the entire journey from raw material to a sellable unit actually sitting on an Amazon shelf.

How do MOQs and defect rates change the true cost?

[04:10]And the article points out that the true economic cost goes even deeper than just the shipping, right? There are these hidden levers that sort of distort the math like minimum order quantities. Yes, the MOQ trap is massive. I mean, I see this all the time.

Right. Let's say factory A charges $10 a unit, but they let you buy 2,000 units. Factory B charges $8 a unit. Looks cheaper. But they demand you buy 5,000 units. So Factory B looks cheaper per unit, but you just tied up $40,000 in inventory when you only needed $20,000 worth to fulfill your current demand. Oh, man. So that extra 20,000 is just trapped. Trapped in a warehouse doing absolutely nothing for your business and it could have been used to you know launch a second product or fund ads.

And then there's the defect rate which honestly that blew my mind when I read it. It's a hidden tax. It really is. If a factory gives you a dirt cheap unit price but like three percent of the units they ship arrive broken or unsellable. Every single good unit has to absorb the manufacturing and shipping costs of those broken ones. Right. So the true economic cost of the inventory is what actually matters. Not that shiny $8 number on the initial quote. Precisely. But, and this is the kicker. Let's assume a seller does all that math perfectly.

Why does when you pay matter, even with the same margin?

Okay. They nail the landed cost. They account for defects. They negotiate a brilliant M.O.Q. They still might sink the business if they ignore the second half of the P.O. The fuel tank in our sports car analogy. The cash schedule. Exactly. So we've proven that the eight dollar quote is often a myth. But even if you perfectly calculate that landed cost down to the penny, you can still run out of fuel.

Why? Because of a concept called payment shape. Payment shape. Okay. Even with identical product margins, the business realities of two different suppliers can be vastly different based purely on when they demand your cash. Okay, give me an example. Imagine supplier A wants 30% of the money the day you place the order and the remaining 70% before the goods even leave the port.

[06:09]Pretty standard, right? Very standard. That's 30, 70 split. Now compare that to supplier B. They only want 20% at the order, but they let you pay the remaining 80% 30 days after the shipment leaves the port. Oh, wow. So with supplier B, the vast majority of my cash stays safely in my own bank account for an extra month or more while the goods are literally on the water?

How long is your cash gone between paying and getting paid?

Yes. And that introduces the most critical metric that almost nobody models correctly, the cash conversion gap. The cash conversion gap. Yeah. This is the agonizing span of time from the moment you make your very first supplier payment to the moment you receive your very first Amazon disbursement from that specific batch of inventory. It really is like a relay race, right? But the baton, which is your working capital, it disappears into a dark tunnel for months. A very dark, very long tunnel.

Right. You hand the cash off to the factory to start production. Production takes what, 30 days? Easily. Then the goods get on a boat, which takes another 30 days. Then they hit Customs, get trucked to an Amazon warehouse, which is another two weeks. Don't forget Amazon's processing time.

Exactly. Then a customer finally buys it, and Amazon holds the funds for another two weeks before actually paying you. You're looking at a dark tunnel of 80 to 90 days where your cash is just entirely inaccessible. And while your profit margin tells you what a unit earns, the cash conversion gap tells you what it costs to wait for those earnings. Cash leaves your ecosystem very early and it returns very late. So, okay, here's where it gets really interesting, because we're basically proving that paying more per unit can actually be a mathematically sound strategy if the timing is right.

Can a more expensive supplier actually be cheaper?

Yeah, absolutely can. Let's look at the defining case study from AmazeBase, because this part completely changes how you evaluate suppliers. The great cheaper paradox. Let's simplify the math a bit so we can really see the mechanism here. Let's do it. Imagine you sell a product for $30.

[08:06]Okay. After Amazon takes their fees, you pay for advertising, all that, you get $12 in cash back per unit. $30 product, $12 in cash back, got it. Now you're evaluating two suppliers. Supplier A can deliver the product to Amazon at a landed cost of $6.80 per unit. $6.80, okay. Their terms are standard, 30% down, 70% before shipment. And because of their production speed and transit route, it takes 75 days for that inventory to travel through the dark tunnel and become sellable. So supplier A costs 6.80 and takes 75 days.

What about supplier B? Supplier B has a landed cost of 7.20 per unit. Wait, wait, stop. Are you telling me I should willingly consider a supplier who charges more per unit? That lowers my profit margins on purpose. Isn't that absolute sacrilege in e-commerce? Why would anyone intentionally choose the more expensive supplier when supplier A is right there?

It feels wrong. I know. But let's look at supplier B's payment shape. Okay. They only require 20% down and the remaining 80% isn't due until 30 days after the shipment leaves. So it's a net 30. Furthermore, their manufacturing process is faster. It only takes them 50 days to get the inventory sellable on Amazon. The instincts of every business owner on Earth scream to take supplier A and protect the profit margin. Supplier A is literally 5.6% cheaper. And that instinct is exactly what traps so much capital. Let's watch what the cash actually does here. Let's hear it.

With the supposedly cheaper supplier A, you have to pay that massive 70% balance before the goods even ship. You are out of pocket for a huge sum. And because they're slow, you don't recover that cash from Amazon sales until much later. But with supplier B, you pay the balance much later and the goods start selling much faster. You actually recover your initial investment 34 days ahead of supplier A. Okay, but I'm still making less profit per unit. How does getting my money back faster overcome the fact that I paid a higher price?

How do capital turns make the pricier supplier win?

[10:12]Because of capital turns. Capital turns. This is the velocity of your money. Imagine you invest $10,000 into inventory. It goes through the dark tunnel and eventually comes back to you as say, $15,000. That entire cycle is one capital turn. Okay, makes sense. If supplier A is so slow that you can only run that cycle 2.8 times a year, you make a certain amount of annual profit. Because it takes so long to get the money back to buy the next batch.

Exactly. But supplier B cycles your money through that tunnel incredibly fast. Even though you make slightly less profit on each individual unit, you are running that same capital through the cycle 3.29 times a year instead of 2.8. Oh, wow. The velocity of the money easily overwhelms the higher unit cost. So the golden rule here is that we have to compare contribution per dollar per year, not just the profit per unit.

That is the secret. When you multiply the unit contribution by their capital turns per year, the expensive supplier B actually earns you $3,200 more annually on the exact same pool of capital. That is nuts. The cheaper supplier literally earns you less money. It really does. And that is before you even factor in the invisible costs of supplier A's sluggishness, like having to tie up even more cash in backup safety stock just to cover their longer lead times. Right, 'cause they take forever.

Exactly. The ultimate constraint on an e-commerce brand's growth isn't usually the unit price. It's how many days each dollar is trapped in the cycle. That completely flips the script on how you negotiate. You aren't just haggling over pennies on the unit cost. You are negotiating for velocity.

Why are the payment dates in your spreadsheet wrong?

Yes. But you know, none of that math matters. If your timing is based on a lie. And in most seller spreadsheets, the dates are absolute fiction. Oh, spreadsheets are a nightmare for this. This is where the structural modeling of the purchase order comes in. We have to stop treating a massive, say, $20,000 P.O. as a single monolithic financial event.

What triggers can a supplier payment have?

[12:03]Because it's not. It's not. It's a series of distinct dated obligations To model those obligations accurately AmazeBase explains that you need to break them down into what they call triggers triggers Okay, the article's four specific triggers that basically cover almost every real-world contract right First you have payments due at order. These are tied to the date you sign the PO, so they are locked in immediately.

Boom. Easy. Second, you have payments due at shipment. These are inherently estimated until the goods actually leave the factory floor or the port. Makes sense. Third, payments due N days after shipment. So the shipment date plus a fixed offset, like that net 30 agreement we talked about. And finally, payments due on a fixed date that you and the supplier just arbitrarily agree upon on the calendar. Okay, but so what does this all mean for my day to day tracking? Like if the spreadsheet date rots, how am I supposed to know when to actually pay them?

What happens to your payment dates when shipping is delayed?

Let's say my second payment is due 30 days after shipment. My spreadsheet says we estimate shipment on October 1st, so the payment is due October 31st. Okay. What happens when a port strike delays the ship by a full two weeks? Does my whole payment calendar just silently rot and become fiction? If you hard code October 31st into your spreadsheet, yes, your system breaks. It silently rots. The ship hasn't left. The payment isn't actually owed yet, but your financial model is screaming at you that you need cash on Halloween.

And I'll be sitting there panicking, moving money around. Making terrible decisions to cover a payment that is actually delayed by a month. So how do we fix the spreadsheet? You never store a date that is derived from an estimate. You must store the trigger and the offset.

Trigger and offset. Right. You store shipment date plus 30 days. That way when reality hits and you update the estimated shipment date to November 1st, the payment due date automatically recalculates to December 1st. Oh, that's brilliant. You keep the inputs grounded in reality, you derive the output systematically, and you clearly label what is a firm date versus an estimated one. It's the difference between a dynamic living cash flow model and a static document that becomes totally wrong the moment a single truck gets a flat tire.

What's the difference between committed, scheduled and due?

[14:10]Exactly. Once you have those dynamic triggers in place, you gain this incredible visibility. You can see the future, but what you usually see hiding in the future is a monster. Yes. Which is why you have to understand the three distinct states of money within your business. AmazeBase defines these as committed, scheduled, and due. Let's break down how a seller actually separates these conceptually. So committed is the total aggregate value of all your open POs. It's the big scary number of what you owe eventually, regardless of when it lands.

Scheduled refers to the specific payment installments that have a trigger attached to them, but haven't been paid yet. It tells you what is coming over the horizon. And then there's due. Right. Due is the immediate threat level. So due is the money that is scheduled and falling inside your immediate operational window, like usually the next 7, 30 or 60 days. Exactly. And this distinction is vital because the true danger to a business isn't usually one massive, expensive product order. Right. You usually see that coming. The danger is the invisible overlap.

What happens when payments from several orders land at once?

The overlap trap. This concept is terrifying. It actually makes me think of juggling. Like, if someone tosses you a 10 pound bowling ball, you can catch it. If they toss you another one 10 seconds later, you catch that too. It's not about how heavy one individual ball is. The danger is when three different bowling balls are falling into your hands at the exact same millisecond. That is the perfect analogy. You look at three different purchase orders for three different products. Let's say they're $10,000, $,000, and $20,000. You pay the 30% deposits on each over the course of a month and feels perfectly fine. The business can afford each of those orders individually.

Right, no problem. But then, because of the varying transit times and those dynamic triggers we discussed, the remaining 70% balances for all three of those POs happened to trigger in the exact same two week window. And suddenly you have a massive cash squeeze. Not because you bought a bad product, but because the payments collided. You know, it's like a pilot staring at just the altimeter while ignoring the fuel gauge and the radar. The business doesn't experience suppliers one at a time. The bank account just experiences a week in which $18,400 evaporates all at once, regardless of whose name is on the invoices.

Is any payment due before its stock brings cash back?

[16:30]Which is why looking at your finances supplier by supplier is fundamentally flawed. Your diagnostic check across your whole portfolio needs to be centralized. You need a system that looks at every dynamic trigger across every PO and asks one specific vital question. And that question is? Is any payment due before the corresponding inventory starts returning cash from Amazon?

Yes. That is the ultimate cash flow monster. It's a strict mathematical comparison of two dates you already have in your dynamic model. Right. If a factory payment is due on November 1st, but the inventory it paid for won't arrive, become sellable, and generate an Amazon payout until November 15th, you have a gap.

A two-week gap. And you have to fund that gap from your existing cash reserves. A dashboard that just lists 50 open POs is useless overhead, but a dashboard that flashes red and says, "These two specific payments will hit your bank account before the cash they depend on arrives." That dashboard just saved your business. Okay, so how do we put this into practice? Let's turn this into a real-world scenario so we're not just listing concepts. Let's say I want to reorder my best-selling product, a garlic press.

What should you check before placing a reorder?

Okay, classic. I go to my computer, I open my supplier portal, and I am ready to hit the Buy button for 10,000 units. What should happen in that moment before I click? Before you hit that button, the framework dictates that you must look at five specific variables on one screen.

Five variables. First, you look at the unit contribution. What does this garlic press actually earn after the true landed cost, Amazon fees, and advertising? Okay, so it earns $4 a unit. Then I look at the cover remaining, right? How many days of inventory do I actually have left in the Amazon warehouse and currently on the water? Right, which directly informs the third variable, the order by date. Based on your dynamic lead times, what is the absolute latest date you can place this PO without running out of stock? So I check that and it says I have to order by next Thursday. Then comes the cash side of the P.O.

[18:27]The fourth variable is cash required and when. You need to see the specific dollar amounts of the installments this new order will create mapped to their future dates. Okay. And finally the fifth variable, the cash recovery date. When does this specific new batch of garlic presses actually start putting money back into your pocket? In variables four and five are the ones almost nobody tracks.

How do your dates and costs get more accurate over time?

Nobody. But comparing the cash required dates against the cash recovery date is what turns a hopeful guess into a hard financial decision. And to get those dates accurate, you don't need to hire a fortune teller, do you? You just look at your own historical supplier data. You have to keep the receipts from the supply chain experiments you're already running every day. Every time you place a PO, you track the promised arrival time versus the actual arrival time. You track the estimated landed cost versus the actual landed cost.

It's empirical data provided by reality itself. Over time, your model doesn't just magically get better. Your assumptions get tighter because they are informed by the history of your own specific supply chain. So, we started this deep dive talking about sports cars and fuel tanks. You want the top speed, you need to calculate the true margin. But if you want to actually finish the race, you have to dynamically map the cash schedule.

Could you pay more per unit to get longer payment terms?

Absolutely. But I want to leave you with a final thought to Chew on building on this entire paradigm shift. If supply chain timing, the velocity of the money through the dark tunnel, is actually a powerful financial instrument, could you intentionally leverage it? Oh, in what way? Well imagine creatively approaching a factory and proposing to pay them a nominally higher unit price, willingly, in exchange for wildly extended payment terms. You say I'll pay you $9 instead of $8, but I want 90 days to pay the balance after the goods ship.

[20:20]Right. If you model the capital turns, you might effectively be tricking the factory into acting as a zero-interest bank to fund your brand's rapid growth. You use the cash you didn't have to pay them up front to launch three entirely new products while still paying the original factory a premium price that keeps them totally thrilled. That transforms the entire nature of supplier relationships. You're no longer squeezing them for pennies on the unit margin. You are actively partnering with them to buy time. It's a whole new track to race on.

Just remember to check the gas tank. Until next time, keep digging deeper.