Bin counts and scans from the plants you stock, drafted as replenishment orders for your rep.

The input is rarely tidy: a handheld scan file, a count sheet from the weekly walk, an email from the crib attendant, or a usage export from the plant's maintenance system. Someone at your branch ties each bin to your item and the plant's part number, works out how many to send from its levels and pack size, prices it from the contract and puts it on the right PO or release.

For the test, AI reads copies of those inputs beside the orders your team built and drafts each replenishment: bin, item, quantity with its working, price source and PO reference. A bin whose min or max doesn't fit its usage gets a note for your rep with the numbers behind it. Nothing is ordered, and no level changes.

The plant's system may be doing the same sum. In SAP, reorder point planning can use the lot-sizing rule SAP calls replenishment up to maximum stock level, the HB indicator in the Lot size field with a figure in the Maximum stock level field: once stock falls below the reorder point, the system proposes enough to reach the max. IBM's Maximo runs a reorder process that creates requisitions or purchase orders for storeroom stock from the reorder point, the economic order quantity, the current balance less reserved and expired stock, and what is on order. Your reviewer should know whether the plant's own reorder still runs on bins you manage. The draft works from your program file's levels and, when you send the plant's records, lists bins where the two disagree.

Counted in one unit, ordered in another. Maximo keeps an item's current balance in its issue unit, and an IBM support note says the reorder process skips an item that has no conversion set between its order unit and its issue unit. Storeroom bins behave the same way: the shelf is counted in eaches or pairs, and the order goes out in boxes, rolls or cases. The draft shows the count unit, the order unit and the conversion it used on every line, and a bin whose count can't be converted goes back to your rep instead of being rounded.

Owned and consigned bins bill differently. Infor's customer consignment guide for Distribution A+ shows the distributor's side: a logical consignment warehouse stands for the customers' sites, tracked by customer and ship-to; stock moves there on a no-charge stock transfer order, which can be generated from minimum and maximum quantities per item; and the customer is billed later on a Customer Consignment Invoice Only order, priced as of the transfer or the invoice. Infor LN's documentation describes both ends: the customer runs the VMI warehouse as a regular warehouse, while the supplier mirrors it as an administrative warehouse because it owns the goods; consumption is recorded by hand or from the customer's call-off message, and the customer may self-bill. The draft keeps owned and consigned bins apart and prices consigned usage on the date your program sets.

Some plants send the data themselves. In X12 EDI, the 852 Product Activity Data transaction lets a trading partner report inventory, sales and other activity so the receiver can plan and ship, or propose, replenishment quantities. Its header has a segment for preassigned purchase order numbers, so a plant can hand out the PO numbers your refills must carry before any order exists. Whatever the format, the draft puts each order on the PO, release or preassigned number your program file names, and holds any order that has none.

What your reviewer watches. Usually the VMI or storeroom program manager, or the rep for the largest plant: each bin mapped to the right item and part number, quantities that follow the levels and pack size, units that convert, contract prices, and consigned bins kept consigned. They also judge the flags, such as a bin that ran to zero between visits, one that hasn't moved in months, or a max smaller than one pack.

When your reviewer says yes against the success criteria, the job drafts replenishments from new counts, scans and usage files for about 30 days.

Your rep or coordinator approves every order before it is entered or shipped, and every flagged level goes to the person your owner named and to the plant, never straight into a program file.

That month is priced as a fixed figure before you sign; a job after it is decided and priced on its own.