Purchase orders and vendor setup for stores: lead times, multiples, and who supplies what

Inventory & replenishment · 10 min read

A purchase order that arrives late is usually not a carrier problem. It is a setup problem that was decided months earlier, on a vendor card nobody has opened since. Three pieces of setup decide most of what a store experiences: the lead time that drives the receipt date, the order modifiers that reshape the quantity, and the item-vendor link that answers the simplest question in purchasing — who supplies what. Get those three right and the order mostly takes care of itself. Get them wrong and every order needs a phone call.

Start with the vendor card, because everything copies from it

Every vendor a store purchases from must be registered with a vendor card, and the purchase codes used on that card have to be set up before the card is filled in. That order matters. A card created before its codes exist gets filled with workarounds, and workarounds get copied onto every purchase document that follows.

Vendor templates are the control against that drift. A template holds predefined information for a type of vendor, so new cards start consistent instead of starting blank. A finished vendor card can be saved as a template, and a template can be applied to one or more selected vendors later — which is the practical way to fix a whole group of cards that were set up the same wrong way. The vendor card is also where the relationship facts live: the items that this vendor and other vendors supply, and the agreements on discounts, prices, and payment methods. Two address details deserve attention at setup, not at payment time. A vendor can carry multiple remit-to addresses — a supplier may ship from a subsidiary but want payment at headquarters — and the correct one is chosen on the Shipping and Payments FastTab of each purchase order or invoice. Alternative order addresses are added from the vendor card with the Order Addresses action. Finally, a hard limit worth knowing before a cleanup project: once a transaction has been posted for a vendor, the vendor card cannot be deleted, because the ledger entries are needed for auditing. Duplicate vendors therefore cannot be cleaned up with a quick delete.

Lead time: the same field exists in four places, and only one wins

The Lead Time Calculation field is a date formula, and it exists on the purchase order line, the Item/Vendor Catalog, the item card, the stockkeeping unit (SKU) card, and the vendor card. When a value is not typed manually on the line, Business Central takes the first one it finds in a fixed priority order. This is the single most misunderstood part of vendor setup, because a correct value in the wrong place does nothing.

The decision rule follows directly: put the lead time at the most specific level that is actually true, and leave the levels above it alone. A vendor-card lead time is a fallback, not a master value — it is used only when no lead time is specified on the item card, the SKU card, or the Item/Vendor Catalog. Stores that set a careful two-day lead time on a vendor card and then wonder why orders still promise two weeks are usually looking at an old value sitting on the item card, quietly outranking the vendor card.

What the lead time then does is arithmetic, in two directions. With a requested receipt date on the line, the system works backward: requested receipt date minus lead time calculation gives the order date — the last day the order can be placed. Without a requested receipt date, it works forward from the order date on the line: order date plus lead time calculation gives the planned receipt date. In both directions, the expected receipt date — the date the items are available for picking — adds two more setup values: planned or requested receipt date, plus inbound warehouse handling time, plus safety lead time. Change the order date on a line and the other dates recalculate. One caution for the backward direction: use date formulas with fixed durations, such as 5D for five days or 1W for one week. Formulas without fixed durations, such as CW for current week, can produce incorrect date calculations when the system works backward.

Calendars sit underneath all of this. A base calendar defined for the vendor or the location affects how the dates are calculated and rounded to working days, so a five-day lead time spanning a vendor's non-working days does not land on the calendar day a buyer expects. If a location works to a significantly different calendar than its vendors, the documented advice is to set up specific calendars for those vendors so lead times calculate properly. For a store, that is the difference between a delivery promised for Monday and a delivery the vendor never intended to make before Wednesday.

Multiples, minimums and maximums: where the case pack belongs

Lead time decides when. Order modifiers decide how much — and they live on the item or SKU, not on the vendor card. The three modifiers are Minimum Order Quantity, Maximum Order Quantity, and Order Multiple. They sit alongside the planning parameters on the same cards: Reordering Policy, Reorder Point, Maximum Inventory, Reorder Quantity, Safety Lead Time, and Safety Stock Quantity. Keeping the two groups separate in your head prevents the most common setup error in this area: hunting for a case-pack setting on the vendor card, where it does not exist.

The retail translation is direct. A vendor who only ships in cases of twelve has handed you an Order Multiple of twelve for every item they supply in that pack. A vendor with a smallest acceptable order has handed you a Minimum Order Quantity. A vendor or a back room with a hard ceiling has handed you a Maximum Order Quantity. When the planning system suggests a quantity, the modifiers reshape it in a set sequence: the quantity is adjusted down to the maximum order quantity, then up to the minimum order quantity, then up to meet the nearest order multiple — with a documented warning that, with erroneous settings, that last step can violate the maximum. That sequence is why a multiple larger than a maximum is not a harmless typo: the system will follow the rules in order and produce a quantity that breaks one of them. Set the three values as a set, check them against each other, and the suggested order arrives already shaped like something the vendor will actually ship.

Where do the shaped suggestions land? The Requisition Worksheet lists the items to order. Lines can be entered manually, or the Calculate Plan batch job can fill the worksheet for items and SKUs set up with a replenishment system of Purchase or Transfer, placing an action message suggestion on each line. The lines are then processed with Carry Out Action Message. None of that machinery invents vendor data — it consumes the lead times, modifiers, and vendor links already on the cards. A worksheet full of nonsense suggestions is a report on the setup, not a fault in the worksheet.

Who supplies what: answer it from the catalog, not from memory

Every store has items that two vendors could supply, items that quietly changed vendor last year, and items one person orders from memory. The Item/Vendor Catalog is the record that settles those questions. For each combination of an item and a vendor it holds the direct unit cost, the lead time calculation, and the vendor's item number. The Vendor Item Catalog report prints exactly that — vendors for selected items, or items for selected vendors — and it exists to compare vendor prices, manage lead time, and manage the vendor relationship from one list. In the United States, Canada, and Mexico, the equivalent is the Item/Vendor Catalog (10164) report. If a combination is missing from that report, the item has no defined supply route from that vendor, whatever the buyer believes. If the vendor's item number is missing, the order goes out carrying an internal number the vendor may not recognise. Clean item-vendor data is not administration for its own sake — systems cannot fix what they do not know, and unknown supply data should be resolved before it is relied on, not after a failed delivery.

Set up a new retail vendor in order

1. Create the purchase codes first. Set up the codes the vendor card will need to select from, before opening the card.
2. Create the card from a template. Choose Vendors, then New, and select the template that matches this type of vendor so the predefined information lands correctly.
3. Complete the relationship facts. Fill or change the fields on the card, add order addresses with the Order Addresses action, and add remit-to addresses where payment goes somewhere other than the supplying address.
4. Assign a purchaser if your store uses them. Purchaser codes identify who buys from this vendor and support statistics and report filtering.
5. Record the agreements. Enter the discounts, prices, and payment method agreed with the vendor on the card, rather than leaving them in email.
6. Build the Item/Vendor Catalog rows. For each item this vendor supplies, add the combination with its direct unit cost, its vendor item number, and a lead time only where this vendor-item pairing genuinely differs.
7. Set the vendor-card lead time as a fallback only. Add a general lead time on the vendor card for items with nothing more specific, knowing any catalog, item, or SKU value will outrank it.
8. Set the modifiers on the item or SKU. Add Minimum Order Quantity, Maximum Order Quantity, and Order Multiple where the vendor's pack or limits require them — and check the multiple against the maximum.
9. Check the calendar. If this vendor works different days than the store's location, set up a vendor calendar so receipt dates round to real working days.

What success looks like

Create a test purchase order for a catalogued item and check three things before deleting it. First, the expected receipt date equals the order date plus the lead time from the highest-priority place that holds a value, plus inbound handling and safety lead time — and you can name which of the four levels supplied that lead time. Second, change the quantity to a number that is not a multiple of the vendor's pack and confirm the planning suggestion reshapes it rather than sending an unpackable quantity. Third, run the Vendor Item Catalog report for the item and confirm the vendor, cost, lead time, and vendor item number you just used all appear on one line. If all three checks pass, the setup — not luck — produced the order.

FAQ

The vendor card lead time is correct, but orders still promise the wrong date. Why? A more specific value is outranking it. Check the Item/Vendor Catalog first, then the item card, then the SKU card — the vendor card is used only when none of those holds a lead time.

Where does a case pack of twelve go? In Order Multiple on the item or SKU — twelve is a quantity rule, not a vendor-card fact. Pair it with the Minimum and Maximum Order Quantities and check the three against each other.

Can a duplicate vendor card just be deleted? Not once transactions have been posted for it — the card is retained because its ledger entries are needed for auditing. Treat duplicates as a cleanup project, not a quick delete.