Can the same calendar apply to multiple suppliers?

Yes. Public holidays, your own receiving calendar and any shared logistics partner can be a calendar that several suppliers reference. Edit once, applied everywhere.

Does the calendar affect the safety stock?

Yes — known longer lead times during a window mean more cover going into it. A four-week closure in August is treated as a four-week lead-time spike for items from that supplier; the safety stock rises ahead of time and falls back after.

Can I add an event in two clicks during a phone call with the supplier?

Yes. Open the supplier card, click a date range, pick the event type ("closure", "lead-time bump", "order day only"), add a note. The change is live on the next planning run.

Inventory & Purchasing

uPurchase

Demand forecasting and purchasing, in one screen.

uPurchase is the demand-forecasting and inventory-intelligence layer Business Central never had. It classifies every SKU, forecasts demand by location, sizes safety stock against a chosen service level, applies supplier calendars and lead times, weighs carrying cost against stockout risk — and then turns the whole picture into concrete, explainable purchase suggestions. Every recommendation answers the question "why" before you have to ask it: the forecast, the safety stock, the lead time and the current position all live on the same row as the quantity. Edit any number and the projected stock curve updates before anything is committed to Business Central. Purchasers get to challenge the numbers instead of trusting them blind, and controllers see service level, stockouts and excess as daily KPIs rather than monthly autopsies.

uPurchase demand chart with historical, future and forecast curves

Functionalities · 10

Advanced tier

uPurchase · Supplier Calendars

Suppliers don't ship every day. Your plan should know.

A calendar per supplier — closures, holiday weeks, temporary lead-time bumps, order-on Mondays only, no-receipt Fridays. Suggestions, lead times and reorder dates all read the calendar before they propose anything, so the plan never proposes a Tuesday delivery from a supplier that ships on Fridays.

Events per supplier

Drop a closure week onto the calendar, a temporary +5 day lead time for a peak period, a recurring "ships Mondays" pattern. Each event has a date range, a type and a short note — visible on every PO and every suggestion that touches the supplier in that window.

Add an event in seconds, during the call

Supplier rings to tell you they're shut the last week of August. Open the supplier card, click the dates, pick "closure", add a note. The next planning run respects it. No master-data ticket, no waiting for IT, no risk of someone proposing a delivery into a closed warehouse.

Receiving calendar too

Closed dock on Fridays? Stocktake the last Monday of every quarter? The receiving calendar prevents arrival dates landing on days nobody can take goods in — and the suggestion is dated so it doesn't.

What you see

Reality, on the calendar.

Most planning systems treat every weekday as identical. Real procurement has rhythm — supplier closures, your own dock hours, peak-season lead times. uPurchase keeps the rhythm visible. A purchaser sees the calendar overlay on the suggestion list and knows immediately why next Monday's order is being proposed today.

Per-supplier closures (single day, week, custom range)
Recurring patterns — "ships Mondays only", "no shipments first week of August"
Temporary lead-time adjustments tied to a date range
Receiving calendar — closed dock days, stocktake periods, public holidays

uPurchase predicted inventory against safety stock and reorder point

When this matters

Signals you'd reach for this.

Christmas catches everyone

Suppliers shut, freight is bottlenecked, your own warehouse is on skeleton crew. Without a calendar, the system happily proposes deliveries that will never arrive.

Peak-season lead times slip

Your usual supplier needs three weeks instead of two from October to December. Adjusting the master data every year is brittle; a dated lead-time event is not.

Some suppliers only ship on certain days

A weekly milk-run, a Monday-only consolidation lane. The plan should respect it, not ignore it and then improvise.

"Why is this dated next Wednesday?"

Without a calendar overlay, every shifted date triggers a question. With one, the answer is on the row.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

The base lead time stays the master-data number. The calendar adds or shifts on top — a closure pushes the receipt date out, a temporary +5 days bump extends it for that window only. When the event ends, the lead time returns to baseline. No manual undo.

See uPurchase in a 30-minute demo.

A real screen-share with someone who built it. No slides.

The uTools suite