Reference · built on requestOperator by FibricInventory & supply

Season Build

Reads last season's weekly demand and the holiday calendar against lead times, then proposes when to start building stock.

Request accessPricing ↗

About

Peaks arrive on a date. Supply arrives after a lead time. Season Build works backward from the one to the other. It reads weekly units sold per SKU from last season's orders, the public holidays for each country you sell into, and the lead time on each item or vendor record in your ERP.

For each SKU it proposes a build start date, the date orders or production must begin so stock is in place before the peak week, and a target quantity taken from last season's demand. A planner reviews the dates and quantities, adjusts for what changed this year, and approves. Purchase orders are drafted only on the approved date.

This is a reference listing. It documents what Fibric would read from Season Build and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Weekly units sold per SKU from order history, filtered by date and SKU, from Shopify or Magento
  • Public holidays by country and year from Nager.Date or the OpenHolidays API
  • Lead time on item or vendor records in your ERP
  • Current on-hand quantity and open purchase orders with requested receipt dates
  • Your own peak calendar: which holidays matter, and the promotion windows you enter

Proposed actions

  • Target capability: propose a build start date per SKU, working back from the peak week by the recorded lead time
  • Target capability: propose a target stock quantity for the peak week from last season's weekly demand
  • Target capability: propose a purchase order or production order draft on the approved start date
  • Target capability: propose a supplier check when a recorded lead time would deliver after the peak

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Start the holiday build on time

    For each SKU that peaked last December, the start date is the peak week minus the vendor lead time in NetSuite, with US holidays read from Nager.Date.

    With Shopify, NetSuite, Holidays & FX Reference

  • Cover a regional holiday you sell into

    OpenHolidays lists holidays by country and subdivision. A SKU that spikes before a regional holiday gets its own build date rather than the national one.

    With Magento, OpenHolidays API

  • Turn last year's peak week into this year's order

    The target quantity is last season's peak-week demand less stock on hand and receipts due. The purchase order draft lands in Business Central on the start date.

    With Microsoft Dynamics 365 Business Central, BigCommerce

Requirements

  • Order history that covers the prior season's peak, from a commerce or ERP connector
  • Lead times held on item or vendor records in your ERP
  • A holiday calendar signal for each country you sell into
  • The peak dates that matter to you: which holidays, and any promotion windows
  • A planner to approve build dates and quantities
Authentication
An ERP API token or OAuth app with read access to items, vendors, and purchase orders, a storefront token with read access to orders, and a holiday feed that needs no key.

Limits

  • A SKU with no sales last season has no baseline. It is listed without a projection.
  • Lead times are read as your ERP holds them. A late receipt last season does not change this season's figure unless you update the record.
  • Holiday dates come from the public feed. Promotion dates and your own peak weeks are entered by you.
  • Business Central's API v2.0 item resource carries inventory but no lead time. There, lead times need another record or a custom API.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Season Build ↗

Questions and answers

What does a planner approve?
A start date and a target quantity per SKU, shown with last season's weekly demand, the lead time used, and the holiday the peak is tied to. The planner can move the date, change the quantity, or drop the SKU.
Does it place orders itself?
No. On an approved start date it drafts a purchase order or production order in your ERP for a buyer to review and send. Nothing is sent to a vendor without that step.
What is kept after a season is approved?
A receipt per SKU per season: the demand it read, the lead time and holiday used, the date and quantity approved, who approved them, and the draft that followed.
Ask about Season Build

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy