Introduction
Ask a merchandiser, a planner and a CFO at the same apparel brand what the company has committed to for the next season. In many businesses, you will get three different numbers.
The line plan sits in a spreadsheet. The buy plan sits in a different spreadsheet, owned by someone else, with a version history nobody trusts. Prebook orders arrive as emailed order forms and get keyed in later. Factory purchase orders live in the ERP. Landed cost is a guess until the container clears. As a result, the season’s true financial exposure is only knowable once three people reconcile files, which usually happens after the money is committed.
Fashion ERP software is an enterprise resource planning system built for apparel operations. It manages style-color-size variants, seasonal collections, pre-season buy plans, prebook orders, wholesale allocation and landed costs in one platform, connecting merchandising, production and finance to the same live data instead of disconnected spreadsheets.
That definition matters less than the workflow behind it. So this article is about the workflow.
THE SEASON IS ONE PROCESS, NOT TWO SYSTEMS
Generic ERP platforms are built around continuous replenishment. Sell an item, reorder the item, receive the item, repeat. Apparel does not work that way. A fashion season is a closed loop with hard dates, and every stage inherits the errors of the stage before it.
The sequence looks like this:
Line plan → Buy plan and open-to-buy → Prebook orders → Factory PO → Production → Allocation → Ship window → Sell-through
Notice that the commitment never changes identity. A unit forecast in the line plan becomes a budgeted unit in the buy plan, then a sold unit in a prebook, then a purchased unit on a factory PO, then an allocated unit, then a shipped unit, then a sell-through data point that informs next season’s line plan.
However, in most brands that single unit is retyped into a new system four or five times along the way. Each retyping is an opportunity for the number to change. The core value of an apparel ERP system is not features. It is that the unit keeps its identity from plan to cash.
STAGE ONE: PRE-SEASON PLANNING
Pre-season planning is where margin is won or lost, because it is where the money gets committed months before any customer signals whether the decision was right.
Building the line plan and seasonal assortment
The line plan defines what the brand will offer: styles, colorways, size ranges, price points and which accounts or channels see which assortment. It is a merchandising document with financial consequences.
In practice, the line plan almost always lives outside the system of record, because generic ERP has no structure to hold it. Consequently, the plan and the purchasing system drift apart the moment a style is dropped or a colorway is added. Nobody updates both.
Forecasting demand when the style has no history
New styles have no sales history, which makes conventional reorder-point logic useless. Apparel planners therefore rely on three practical methods:
- Like-item forecasting. Forecast the new style against a comparable style from a prior season, adjusted for price and placement.
- Channel-level splits. Wholesale, retail and direct-to-consumer sell the same style at different rates, so a single blended forecast hides the risk.
- Sell-through assumptions by door type. A flagship account and a regional independent do not behave alike.
An ERP supports this by holding the forecast as structured data rather than as a spreadsheet tab. Business Central’s demand forecast, for example, can be set at item and location level, which means the plan can distinguish the East Coast distribution center from the West.
Converting the plan into a buy plan and open-to-buy
The buy plan turns forecast units into committed dollars. It has to respect factory minimums, fabric lead times and the open-to-buy budget finance has approved.
This is the handoff that fails most often. When the buy plan is a spreadsheet, open-to-buy discipline depends on someone remembering to update it. When a factory PO date slips by three weeks, the buy plan does not know. Moreover, the finance team’s cash forecast does not know either.
What breaks without an ERP
To be concrete, here is what the spreadsheet version costs:
| FAILURE | ESSENTIALS |
|---|---|
| Buy plan version conflicts | Two teams commit against the same open-to-buy dollars |
| Lead times held informally | Late buys, air freight, margin erosion |
| Landed cost unknown until receipt | Style-level margin is a guess during the buy |
| No plan-to-PO traceability | Nobody can explain why the season over-bought |
STAGE TWO: PREBOOKS AND FASHION ORDER MANAGEMENT
Prebook is the mechanic that separates apparel from almost every other industry, and it is the part most fashion ERP content skips entirely.
Selling inventory that does not exist yet
In wholesale apparel, buyers commit at market weeks or through line sheets, months before goods are produced. The brand is selling future supply against a factory order that has not shipped, and sometimes has not been placed.
Standard Business Central has a mechanism that maps to this: the blanket sales order. Per Microsoft’s documentation, blanket sales orders are visible to the planning engine as demand and are reflected in forecast projected inventory, so a prebook commitment can influence what gets purchased. That is a genuine capability, and it is more than most teams realize they already own.
The ceiling appears at the variant layer, which the next section covers.
Allocation when supply lands short
Containers arrive short. Factories cut a color. A style over-sells. Someone then has to decide which accounts get the units.
Done well, allocation runs on rules: account priority, order date, channel protection, substitution logic where a customer has pre-approved an alternative. Done in a spreadsheet, allocation runs on whoever emails loudest. Consequently, brands quietly damage their best wholesale relationships and rarely attribute the lost account to the allocation process that caused it.
Partial shipments, backorders and the ship window
Retailer cancel dates are unforgiving. A partial shipment decision is therefore a margin decision: ship what is ready and eat the split-shipment freight, or hold and risk cancellation. An ERP that tracks the full order lifecycle, including partial shipments, backorders and substitutions, lets that call be made with numbers rather than instinct.
Trading partner compliance
Advance ship notices, labeling standards and routing guides generate chargebacks when they fail. Importantly, most compliance failures are data problems before they are warehouse problems. If the order, the item master and the customer requirements do not agree inside the system, the warehouse cannot ship compliantly no matter how careful the team is.
CLOSING THE LOOP: SELL-THROUGH AND LANDED COST
Once goods ship, two data sets determine whether the next season is smarter than this one.
Sell-through by collection, channel and location shows what is actually moving. This is the real test of fashion inventory management software: it should drive reorder decisions while there is still time to reorder, and markdown decisions while the markdown is still small.
Landed cost determines whether the margin on the line plan was real. Business Central handles this through item charges, which allocate freight, duty and handling costs onto received items so that inventory value reflects true cost rather than invoice cost.
Together, these feed next season’s line plan, which returns the process to Stage One. That is the loop, and an ERP’s job is to keep it closed.
WHAT THIS LOOKS LIKE IN MICROSOFT DYNAMICS 365 BUSINESS CENTRAL
Business Central is a strong foundation for apparel finance and operations. Out of the box, it delivers general ledger and multi-entity consolidation, purchasing, warehouse management, item variants, demand forecasting, requisition and planning worksheets, item charges for landed cost, and Copilot-assisted workflows. Notably, its planning engine already works at the item, location and variant level, so SKU-level planning is native rather than bolted on.
The ceiling is structural rather than a shortcoming, and it is the reason dedicated apparel ERP software exists. Standard item variants in Business Central are a flat list of variant codes attached to an item. A style with eight colors and six sizes therefore requires forty-eight variant codes created and maintained individually. Multiply that across a 200-style line and master data becomes the bottleneck. Standard variants also carry no inherent relationship, so there is no native concept of “all sizes of this color” for allocation or reporting.
That gap is precisely what Volt 365® Apparel closes. It is a native AL extension running inside Business Central, not middleware or a separate system, and it adds the apparel layer the platform was never designed to carry: up to four product dimensions with automatic SKU generation, catalog and assortment management, prebook and wholesale workflows, allocation and substitution, pack sizes, landed cost visibility, and margin reporting by collection and channel.
For a deeper technical treatment of where the standard platform stops, see why standard Business Central falls short for apparel brands and how footwear brands scale on Volt 365® Apparel.
Volt implements this for apparel, footwear and accessories brands, typically in the $20 million to $300 million revenue range. Allure Bridals is one example, and Volt’s fashion client base includes brands such as Rag & Bone and Canada Goose.
A PRE-SEASON READINESS CHECK
Before evaluating vendors, run this diagnostic on your current setup. Each question is a yes or a no.
- Can you see committed prebook quantities against open factory POs on one screen?
- Does your buy plan update automatically when a PO delivery date slips?
- Can you allocate short supply by rule rather than by negotiation?
- Is landed cost applied at PO stage, or only at receipt?
- Can you report sell-through by collection without exporting to Excel?
- Do vendor lead times live in the item record rather than in someone’s memory?
- Can your sales team enter orders across a size-color grid in one action?
- Does compliance validation happen before shipment or after a chargeback?
- Can finance close the period without reconciling a planning spreadsheet?
Six or more “no” answers means the constraint is the system, not the team. Additionally, timing matters: start the evaluation between seasons, not six weeks before market.
CONCLUSION
The distinction between pre-season planning and order management is an artifact of the tools brands have used, not a real division in the business. One is the forecast of a commitment and the other is the fulfillment of it. When both live in the same system, alongside landed cost and sell-through, the season becomes a managed process rather than a series of reconciliations.
Business Central provides the financial and operational foundation. The apparel-specific layer, meaning variants, assortments, prebooks and allocation, is what turns that foundation into a genuine ERP for the fashion industry rather than a general ledger with clothes in it.
Frequently Asked Questions
Fashion PLM manages product development: design, tech packs, specifications and approvals. Fashion ERP manages commitments, costs and inventory: purchase orders, prebooks, allocation, landed cost and financials. Most brands above a certain scale run both and integrate them.
Through future-dated sales commitments that the planning engine treats as demand. In Business Central, blanket sales orders serve this purpose and are visible in forecast projected inventory, so prebook demand can drive purchasing decisions before goods are produced.
Yes, provided the system supports channel-level allocation. The requirement is not shared inventory visibility alone but the ability to protect or prioritize supply by channel, so a DTC surge does not consume units already committed to a wholesale account.
The practical trigger is not revenue but reconciliation time. When closing a season requires manual reconciliation between the buy plan, the order book and the ERP, the spreadsheet has become the system of record and the risk is no longer manageable.
Timelines vary by scope, data quality and integration count, so any fixed number is misleading. The more useful planning rule is to align go-live with a gap in the buy calendar rather than with a fiscal date, because cutting over mid-buy compounds risk unnecessarily.
