One build. Then a weekly rhythm.
We model your catalog once, properly. Then a planning cycle runs every single week, whether or not you had a good week.
The build, week by week.
Your time cost across the whole build is one structured handover at the start and one sign-off walkthrough at the end. We do the digging. You answer questions.
One handover
A one-page checklist goes out: your platform exports, 3PL data, supplier list, and open POs. No credentials are needed to start, because the build runs off exports pulled from your own systems. Whatever shape your data is in, that is the normal starting point and not a disqualifier.
The first working sheet
The combined inventory and demand view across every node, in a first working version. This is the fastest visible proof that the build is not going to cost you weeks of calendar. A client’s words on this artifact: “you did this in a day. Not four weeks.”
Stop the bleed, first
The Sunset Tab and the Reconciliation Layer land early, ahead of the rest, because they are the fastest to produce and the most likely to pay for the build before the build has even finished. The reimbursement sweep and the overstock scan run in parallel.
The model
Master sheet population, the PO tracker, the forecast engine, and per-supplier calibration of the 23-stage lead-time model. This is where your Q4 and Chinese New Year order-by dates stop being a guess and start being an output.
Sign-off walkthrough
Every material finding named out loud, with the evidence on screen, and you correct anything we got wrong before the weekly rhythm starts. The Owner-Liberation Ladder is handed over here as a written document, not narrated on a call.
The weekly cycle starts
From here the plan lands before your call, every week. The rest of this page is what that actually looks like.
The cycle.
Four moving parts. Only one of them costs you time.
The plan lands before the call
Every SKU that needs an order, with the quantity, the supplier, and the order-by date. Every transfer worth making this week. Every risk flag, ranked, each with a reason attached. It arrives whether or not anyone chased it. We move
The call, on the decisions and not the data
Your account lead walks the decisions. You say yes, no, or “not that one, here is why.” That context goes back into the system, so next week’s plan is sharper. This is the only calendar cost you carry. You move
The approved plan gets run
On Core, you place the POs and run the transfers with the plan in hand. On Partner, we do it: POs placed in your name, transfers run, suppliers and forwarders chased live until goods are checked in. Depends on tier
The watch between calls
Coverage gaps projected forward. Velocity spikes past twice baseline flagged and reviewed by an operator, not fired off automatically. Committed-versus-actual ETAs chased on a fixed cadence. When something breaks, you hear about it while it is still cheap to fix. We move
One workbook. Every question already has a tab.
The weekly plan is one tab of several. The others answer the questions that come up between calls, so nobody builds a new sheet to ask them.
=IF( AND([@[DOC FBA]] < 21, [@[Units 3PL]] > 0), "TRANSFER", "" )| A | B | C | D | E | F | G | H | |
|---|---|---|---|---|---|---|---|---|
| 1 | Amazon SKU | DOC FBA | DOC AWD | DOC 3PL | Units FBA | Units AWD | Units 3PL | Send to |
| 2 | EM-SCT-02 | 11 | 0 | 149 | 310 | 0 | 4,220 | FBA · 640 |
| 3 | PT-BED-03 | 41 | 0 | 74 | 880 | 0 | 1,240 | FBA · 400 |
| 4 | CK-PAN-12 | 38 | 0 | 88 | 740 | 0 | 1,980 | AWD · 900 |
| 5 | CK-DUO-08 | 61 | 27 | 112 | 1,840 | 960 | 2,410 | — |
| 6 | GR-MAT-07 | 78 | 34 | 141 | 2,240 | 1,100 | 3,050 | — |
The transfer tab: one node running thin while stock sits at another.
=[@[This week]] - [@[Last week]]| A | B | C | D | |
|---|---|---|---|---|
| 1 | Metric | This week | Last week | Δ |
| 2 | SKUs below reorder point | 4 | 7 | −3 |
| 3 | SKUs at risk in 30 d | 2 | 1 | +1 |
| 4 | Units aged past 180 d | 12,010 | 13,640 | −1,630 |
| 5 | Open POs past ETA | 1 | 3 | −2 |
| 6 | Nodes reconciled | 4 / 4 | 3 / 4 | +1 |
| 7 | Cash in overstock | $61,400 | $68,900 | −$7,500 |
The health snapshot: six lines, same six every week, so the direction of travel is visible before anyone opens a tab.
The slower loops.
Not everything belongs on a weekly clock. These run on their own cadence and land in the same plan.
Monthly
The stock valuation at cost across every location, which is the number your P&L stands on. The five-point account health check. A one-page review of what moved and what did not.
Quarterly
Supplier scorecards, generated from data the system already captures rather than assembled by hand. A refresh of the sunset and rationalization pass, and of the seasonality factors.
Twice a year
Peak-season programs, built backward from real landing dates: Q4 stock landing by roughly mid-October, and Chinese New Year orders placed before the factories close on their own schedule.
The dashed line is where a 60-day assumption runs out. Everything to its right is the gap most brands discover only after a stockout. Calibrated per supplier and per shipping mode, so your dates are yours and not an industry average.
You should be asking about this.
Handing account access to a vendor you just met is a legitimate concern. The right answer is not to ask for your trust. It is to structure access so that trust is not what is holding it together.
Owner and full adminNever requested
- Owner login
- Full-admin role
- Payment methods
- Bank detail edits
Scoped rolesWhere we work
- Your platform’s own permission system
- The shared workbook
Whatever your platform’s own roles already allow, and nothing custom or elevated on top of them.
Nothing in the first box is asked for at onboarding, once trust has built, or at any later phase. Everything in the second is revocable by you at any time, without asking us, and anything touching a payment is confirmed live on a video call before it is actioned.
Scoped access only, never root
We work inside your platform’s own role-based permission system. Never a full-admin or owner login, on any engagement.
No payment-method or bank-edit rights. Ever.
Not at onboarding, not once operational trust has built up, not at any phase of the engagement.
Payment changes are verified live
Anything touching a bank detail or a payment is confirmed on a video call before it is actioned, rather than pushed through quietly.
You control it, and you can revoke it
You retain full visibility into exactly what has been granted, and you can withdraw any of it at any time without asking us.
This is not a policy written for a web page. It is how access is scoped on every engagement, because the risk is real and the fix has to be structural.
Thirty minutes, then you decide.
Thirty minutes on a free call. You almost certainly know which SKUs are tight already. The harder part is the order-by date sitting behind them, the cash that has quietly stopped moving, and where your three systems disagree. That’s the conversation.