Replenishment
Track each brand's reorder cycle from due through to complete, send the brand its weekly replenishment request, and keep the purchase orders for that cycle attached to it.
Replenishment turns each brand's weekly reorder into a tracked cycle instead of a spreadsheet. You see which brands are due, work each cycle through its status pipeline, send the brand a replenishment request to approve or edit, and keep every purchase order for that cycle attached to it.
Who sees what
NC Super Admins and NC Internal Users work every screen here, each on their own accounts. Brands (Client Users) open Replenishments read-only for their own accounts, as set out in What brands see. Accounts stays with NC staff, and a direct link sends a brand back to the dashboard. See Roles and access.
The Replenishment section of the sidebar holds Accounts, then Replenishments (the Cycles screen below), then the Replen Report. Brands see Replenishments and the Replen Report.
Accounts
The Accounts screen lists every account with the figures that tell you whether it needs a cycle started.
| Column | What it means |
|---|---|
| Reorder Cadence (Days) | The reorder interval you set for this account. Edit it in place. |
| SKU-Derived Cadence | The shortest non-zero order interval across the account's SKUs. Reference only. |
| Days Since Last Cycle | Days since the account's most recent cycle. Blank if it has never had one. |
| Current Cycle Status | The status of the account's current open cycle, if one is running. |
Reorder Cadence is the one that matters. Type a number of days and it saves when you click away or press Enter. Clear it and the account stops being tracked for due dates.
SKU-Derived Cadence is shown next to it for reference and nothing runs off it. It is the shortest non-zero interval across the account's SKUs, so a single fast-moving item pulls it down and it rarely reflects how the account is actually ordered.
Due / Overdue
The Due / Overdue button filters to accounts where Days Since Last Cycle has reached the Reorder Cadence you set.
An account with no Reorder Cadence entered never appears here, and neither does one that has never had a cycle. Set a cadence to start tracking it.
Filters
Filter by current cycle status, reorder cadence, and a minimum number of days since the last cycle, or search by account name. Clear resets everything.
Starting a cycle
Start Replenishment on a row, or New Replenishment at the top, opens the create form. Pick the account and the period start date. The period end date fills in automatically from the account's cadence and you can change it. Cycles are created one at a time.
Creating the cycle also takes a snapshot of the account's Replen Report and puts it on the cycle as its replenishment request. The cycle then opens on its Replenishment Request tab with the magic link ready to send, so there is no trip to the Replen Report first.
Cycles
The Cycles screen lists cycles across every account, with the status each one sits at and how long it has been there. Days in Status turns orange once a cycle has sat in the same status for more than three days.
New Replenishment at the top opens the same create form as on Accounts and takes the same Replen Report snapshot. See Starting a cycle.
New Replenishment at the top opens the same create form as on Accounts and takes the same Replen Report snapshot. See Starting a cycle.
The Draft PO Status and ShipHero PO Status columns are read from the purchase orders attached to the cycle rather than stored on the cycle itself, so they always match what the POs actually say.
The Replenishment Request column works the same way. It shows the status of the cycle's open replenishment request: orange while it awaits the brand's response, green with the time once they respond, and Drafts created after the draft POs are made. Cycles without a request show a dash.
Editing from the list
Period start, period end, and status are all editable in place. Change one and it saves straight away, so moving a cycle along does not need a trip into the detail screen. Clicking anywhere else on the row still opens the cycle.
Filters
Filter by account, cycle status, draft PO status, ShipHero PO status, and a period date range, or search by account name.
Deleting a replenishment
Test and placeholder replenishments can be deleted so they stop counting. Click the bin icon at the end of the row, or Delete at the top of the replenishment. NC staff see both. Brands never do.
The dialog asks "Delete replenishment #22 for Vitamin Well (ShipHero)?" and, when there are any, says how many of its draft POs and requests are hidden with it. Click Delete to confirm.
A real purchase order blocks the delete
A purchase order ShipHero knows about makes the replenishment real: a synced ShipHero PO on its Purchase Orders tab, or a draft that was submitted to ShipHero or set to ShipHero PO Created. The dialog names those POs and asks you to unlink them on the Purchase Orders tab first. Unlinking keeps the PO itself.
A deleted replenishment is left out everywhere replenishments are read:
- The Replenishments list, every filter, and the count above it.
- Current Cycle Status and Days Since Last Cycle on Accounts, which go back to the account's previous replenishment.
- The open cycle the Assistant attaches new drafts to.
- Its draft POs on the Purchase Orders list, and its requests on the magic link's History.
Its page reads "This replenishment was deleted.", and the magic link of any of its requests reads "This request is no longer available." and takes no response. Its drafts can't be submitted to ShipHero, even from an old link.
Delete is a soft delete. The record stays in the database with when and by whom it was deleted. There is no restore screen, so ask OpsKings to restore one deleted by mistake.
Cycle detail
Opening a cycle shows where it stands and everything attached to it. It opens
on the Replenishment Request tab, followed by
Purchase Orders, Details, and Status Timeline. A link that names a
tab, ending in ?tab=purchase-orders for example, opens that tab instead.
Brands see the same tabs without Status Timeline. See
What brands see.
Status pipeline
A cycle moves through this pipeline:
| Status | Meaning |
|---|---|
| Internal Draft | The cycle has been created and the team is preparing the order. |
| Order Submitted to Client | The order has gone to the client. |
| Client Confirmed Order | The client has confirmed it. |
| POs Confirmed Created | The purchase orders are placed. |
| Replenishment Completed | Everything has arrived and been scanned in. |
| Cancelled / Archived | The cycle was abandoned. |
The Status dropdown at the top of the cycle shows where it sits and moves it to any status. Nothing advances on its own, so moving to POs Confirmed Created and to Replenishment Completed are both deliberate steps you take once the work is actually done.
Statuses carry their number, so 200 Client Confirmed Order in the app is the
same status the team calls 200. Two read differently on screen than they are
stored: Internal Draft is 000 New and Replenishment Completed is
1000 Cycle Completed.
Statuses NC no longer uses
Replen Review In Progress (050), Followed Up For Client To Process Order (299), and Client Processed Order (300) are not offered in any status dropdown or filter. A new cycle goes straight into Internal Draft, and a brand confirms its order once, so those steps were cut. The values still exist in the database, so a cycle that already passed through one keeps that row on its Status Timeline.
Every move records its timestamp, which is what drives Days in Status and Days Since Last Cycle. The Status Timeline tab shows when the cycle entered each stage.
Purchase Orders
The Purchase Orders tab lists every PO on the cycle with its status, warehouse, tracking number, and the inbound and received quantities read from the synced ShipHero PO.
Add Purchase Order gives you two ways to attach one:
- Create Draft builds a draft PO already attached to this cycle. Pick the vendor and warehouse. Add line items and submit it to ShipHero from the Purchase Orders screen.
- Link Existing PO attaches a ShipHero PO that has already synced, for when the PO was placed without going through the draft flow. Start typing a PO number to search. An account can have hundreds of purchase orders, so the search runs against all of them rather than only what is on screen.
A draft moves through Draft, then PO In Progress once you have started placing it, then ShipHero PO Created. Submitting a draft to ShipHero sets the last one for you.
Tracking numbers
A tracking number lives on the draft purchase order. A PO linked directly to a cycle, with no draft behind it, has no tracking number to show because the synced ShipHero PO record does not carry one.
Unlink removes a PO from the cycle without deleting the purchase order.
How a draft and its real PO stay paired
When you submit a draft to ShipHero, the app records the id of the purchase order ShipHero created. The real PO arrives in the portal later, through the ShipHero sync, which knows nothing about cycles and so writes it with no cycle attached.
The cycle closes that gap itself. Opening a cycle matches any purchase order whose ShipHero id equals one recorded on its drafts, attaches it, and saves the link so it is done once rather than worked out every time. No matching on PO name is involved, so a renamed or duplicated PO name cannot break it.
A PO already on another cycle is left alone
If the matching purchase order is already attached to a different cycle, nothing is moved. That is a question for a person rather than something to reassign quietly, so unlink it from the other cycle first.
What brands see
Brands open Replenishments to check where their reorders stand without asking NC. They see only their own accounts' replenishments, and they can't change anything on them.
| Where | What a brand sees |
|---|---|
| The list | Account, period, status, days in status, and ShipHero PO status. |
| Replenishment Request tab | The open request's magic link, with Open request and Copy magic link. |
| Purchase Orders tab | The ShipHero POs on the replenishment, with their status, warehouse, inbound, and received. |
| Details tab | The status and the period. |
With no open request, the Replenishment Request tab reads "No replenishment request on this replenishment yet."
Everything else stays with NC staff:
- New Replenishment, the status dropdown, editing the period dates, and Delete.
- Add Purchase Order, the draft status, and Unlink.
- Draft POs: the Draft PO Status column and filter, tracking numbers, and drafts on the Purchase Orders tab.
- The Replenishment Request column and the Awaiting Client To Process Order view.
- The Status Timeline tab.
- On the Replenishment Request tab, the snapshot, counts, notes, lines, draft PO links, left-out lines, replaced requests, Create draft POs, and Download for ERP (CSV). The brand works the request on its magic link instead.
A pushed PO shows up once NC opens it
A PO pushed from a draft attaches to its replenishment the next time NC staff open Replenishments or that replenishment, as described in How a draft and its real PO stay paired. Until then the brand doesn't see it on the Purchase Orders tab.
The server enforces all of this, not just the screen. A brand asking for another account's replenishment gets "not found", and every change is refused. To check the brand's view yourself, use Preview as client.
Replenishment requests
A replenishment request is the weekly order you send a brand for one cycle. You can adjust it first. The brand then opens it through a magic link, approves or edits each line, and submits. You turn the response into draft POs without re-keying anything. For the steps in order, see Send a replenishment request.
Everything in a request is counted in trays. A tray is one base unit, and a Case SKU holds about 12 trays. Each line carries two numbers:
- Recommended is the Replen Report's Amount To Reorder for that SKU and warehouse, as it was when the request was made. It never changes. Orders excluded from metrics don't count toward the demand behind it. A line NC adds after the request was made has no Recommended, since the report didn't ask for it.
- Requested is what NC asks the brand for. It starts at Recommended, and you can raise it, lower it, or delete the line until the brand responds. You can also add lines the report left out. See Adjusting the request.
The brand only ever sees Requested.
Creating a request
There are two ways to create one. Both take the same kind of snapshot and land you on the cycle's Replenishment Request tab.
By starting a cycle. Creating a cycle from the Accounts or Cycles screen takes the snapshot for you. It uses the Replen Report's default view of the account: every warehouse, active SKUs only.
From the Replen Report. On the Replen Report, filter to one account. Create Replenishment Request appears next to Run Report and Export CSV, for NC staff only. It opens a popup where you pick the account's open cycle, or click New replenishment to create one. Confirming takes a snapshot of the report and opens that cycle on its Replenishment Request tab. This snapshot holds the rows the report is showing, so a warehouse or SKU Activity filter you set narrows it. Use this way to narrow a request or to add one to a cycle that already exists.
Either way, the snapshot holds the account's lines with Amount To Reorder above 0, one line per SKU per warehouse, with Amount To Reorder as each line's Recommended and the Requested it starts at. Each line's Item # and Flavor are its Base SKU's code and name, the same SKU the Replen Report lists. That matches the quantities, which are in Base SKU units. The brand's link, its History, the Replenishment Request tab, and the ERP CSV all name lines this way. Only the draft POs use the Case SKU.
If the report lists the same SKU and warehouse more than once, the request takes it once, with the larger Amount To Reorder. A row with no SKU or no warehouse is left out. Neither stops the request from being created.
One snapshot per request
A cycle created with the popup's New replenishment button takes no snapshot of its own. The popup takes the one snapshot when you click Create Request.
If none of the account's active SKUs has an Amount To Reorder above 0, the cycle is still created. Its Replenishment Request tab says No lines need reordering, and there is no link to send yet. Create the request from the Replen Report once lines need it.
If the report can't be read while the cycle is being created, the cycle is kept and an error says its lines could not be added. Create the request from the Replen Report instead.
A cycle can have more than one request, but only the latest is open. Creating a new request for the same cycle closes the earlier link, which then shows "Replaced by a newer request".
The brand's link
The link needs no login. It shows the account, the cycle start date, when the request was made, and its warehouses, then one list grouped by SKU with a SKU total row, so the brand decides against each SKU's total across warehouses. The total row shows the SKU's Item #, Flavor, total Required, its decision counts, and total Approved, with its warehouse lines listed under it. Filters for warehouse and SKU and a search on SKU or flavor narrow the list.
Each warehouse line shows one number, Requested, which is NC's figure. The Replen Report's Recommended is not on the brand's link at all, and lines NC deleted don't appear.
On each warehouse line the brand picks:
- Approve, which copies Requested into Approved.
- Edit, which opens Approved for any whole number of trays from 0 up to one less than Requested. There is no pallet or multiple check. The line then shows Edited, and the SKU total row counts it, for example "1 approved · 2 edited".
Add SKU adds one of the account's SKUs that isn't on the request, such as a launch with no demand yet. The brand searches the account's active Base SKUs by code or flavor and picks one, ticks each warehouse it goes to, and enters the trays they approve for each. Flavor fills in from the SKU, and each warehouse becomes its own row at the bottom of the list. SKUs already on the request show Already included in replen and can't be picked, and there is no way to type in a SKU that isn't in the system. Until they submit, the brand can change an added row's Approved or delete the row with its bin icon.
One Any notes for National Commerce box takes a note for the whole request.
The footer keeps running counts: lines, approved, edited, to decide, new SKUs, total Requested, and total Approved. An edited amount outside 0 to one less than Requested, or an added SKU's amount that isn't a whole number of 1 or more, isn't counted in Approved until it's fixed. Submit response only enables once every line has a decision and every added SKU has its amount. The brand can submit once. After that the lines are read-only, and Download for ERP (CSV) becomes available. The link never expires.
The brand never sees the cycle end date
Brands read an end date as the day their order will deliver, so the link shows only the cycle start date and the brand's CSV has no Cycle End column. The end date is for NC's own planning. The cycle detail, the Cycles list, and NC's own download keep it.
If NC changes the request while the brand has it open
When NC changes, deletes or adds a line, the submit is refused and the page shows the latest numbers. The brand's decisions stay: an approved line picks up the new Requested, an edit that no longer fits is flagged, and a line NC added waits for a decision. If NC added a SKU the brand had also added, the brand's own row reads Already included in replen and has to be deleted. They check the lines and submit again, so they never agree to a number they didn't see.
History is for NC staff only
The link has a History tab with the account's past requests under their cycle and an Edits by SKU view: per SKU, the weeks it was requested, the weeks it was edited, and which weeks. The tab only appears for someone signed in to the portal as NC staff. Brands opening the link never see it.
The Replenishment Request tab
The tab on the cycle shows the latest request: when the snapshot was taken, whether the brand has responded, Copy magic link, the summary counts, the same filters and grouped list, and the brand's notes. SKUs with no Case SKU carry a No case SKU flag. Requests that were replaced are listed below it, read-only.
The list has a Recommended column beside Requested, and the SKU total rows and summary counts show both totals. A Total row at the bottom of the list adds up Recommended, Requested, and Approved for the lines the filters show, so it narrows with them. The summary counts always cover the whole request. A line where Requested differs from Recommended carries an Adjusted badge, with how far it moved (for example −20 or +50) next to Requested. A line NC added after the request was made carries an Added badge, and its Recommended is blank. Both marks stay after the brand responds, so you can always see which lines NC changed.
Once the brand has responded, Download for ERP (CSV) gives you the brand's file with one more column, Cycle End.
Brands see only the magic link on this tab. See What brands see.
Adjusting the request
The Replen Report is often wrong for a given week: a SKU was out of stock lately, a promotion is coming, a new SKU has no history, or you already know the brand is out of an item. Fix those lines before the brand responds.
- Change Requested by typing a new number in the line's Requested box. It saves when you press Enter or click away, and Escape puts the saved number back. Requested is a whole number of trays, 1 or more, and it can go above Recommended.
- Delete a line with the bin icon at the end of the row, then confirm. The line leaves the list, its SKU total, the summary counts, and the brand's link. The record is kept with when and by whom it was removed.
- Add a SKU that isn't on the request with Add SKU under the list. Search the account's active Base SKUs by code or flavor and pick one. SKUs already on the request show Already included in replen and can't be picked. Flavor fills in from the SKU. Tick each warehouse it goes to and enter its Requested, then click Add line, or Add 2 lines for two warehouses. Each warehouse becomes its own line, and the SKU goes to the bottom of the request and stays there. A SKU can be added whatever its Amount To Reorder, so a launch with no demand yet still makes this week's request.
- Add a warehouse to a SKU already on the request with the + in its Warehouse column. Pick one of the account's warehouses the SKU isn't on yet, enter Requested, and press Enter or click Add. The new line goes under the SKU's other warehouses.
Added lines carry an Added badge and work like any other line: you can change their Requested or delete them, the brand approves or edits them, and they go onto the draft POs. Only active Base SKUs are offered, as on the Replen Report. To add an inactive one, mark it active first on Reorder Point Settings. The warehouses offered are the ones linked to the account.
A request keeps at least one line, so the last one can't be deleted. To drop everything, create a new request from the Replen Report instead.
Only until the brand responds
Editing, adding, and Delete are on the latest request while it awaits the brand. Once the brand submits, the request is read-only, and replaced requests are always read-only.
Creating draft POs from the response
Create draft POs turns the response into one draft per warehouse, attached to this cycle. The drafts use the same records, PO-number naming, and vendor as the Create Draft form. The vendor is picked for you when the account has one, and asked for when it has several.
Every draft line is on the Case SKU and named by it. Its quantity is Approved trays divided by the Case SKU's units per case, rounded down to a whole case. Approved came from NC's Requested, so a line you lowered from 100 to 80 and the brand approved is drafted from 80 trays, not 100. Lines NC added and SKUs the brand added are drafted the same way.
Nothing is dropped silently. These lines stay off the drafts and are listed under Left out of the draft POs for you to handle, in trays and under their Base SKU like the list above:
- Trays left over below a full case.
- Lines edited to 0.
- Lines with no Case SKU.
- New-SKU rows the brand typed in before brands picked from their SKUs. These have no Base SKU to put on a draft.
Links to the new drafts then show on the tab. Each opens the draft on the Purchase Orders screen, where you review it and click Submit to ShipHero as usual. If some drafts fail to save, clicking Create draft POs again creates only the missing ones.
Download for ERP
The brand's CSV, downloaded from the magic link, has exactly these columns: Item #, Flavor, Warehouse, Quantity (Approved trays), Unit (trays), Cycle Start. The CSV from the cycle's Replenishment Request tab adds Cycle End as a last column. Item # and Flavor are the Base SKU's code and name, as on the screens. Both have one row per approved line. Lines edited to 0 are left out and SKUs the brand added are included, named by their Base SKU like every other line. An older new-SKU row the brand typed in keeps the Item # and Flavor they typed.
The columns may change
The columns are a best guess at the brand's ERP upload format. They will be adjusted once the Dynamics upload format is confirmed.
Related
Send a replenishment request
Create the request, share the link, and turn the brand's response into draft POs.
Purchase Orders
Build drafts, push them to ShipHero, and check receiving.
Replenishment cycles table
The cycle record and its links to the PO tables.
Inventory
Replen report, snapshots, and reorder point settings.