Negotiate from the plan,
not against it.
Sourcing decides who makes what, at what cost, by when — and those decisions set the season’s margin. But sourcing usually works blind to the assortment plan, with vendor history scattered across email threads and IMU targets out of date by the time RFQs go out.
RetailNorthstar gives sourcing the demand signal, MOQ visibility, and vendor performance history needed to commit with confidence — and to renegotiate when the plan moves.
The strategic decisions get made on incomplete information.
Sourcing teams are asked to commit cost, capacity, and lead time before the assortment is locked — and to absorb every plan change as if their commitments were infinitely flexible.
Costing happens before the assortment is set
You are quoting vendors against a target IMU built from last season's averages, while merchandising is still finalizing styles. By the time the plan is locked, your costs are already committed — and the IMU shifts under you. Re-costing mid-cycle eats days.
Vendor capacity conversations happen in a vacuum
You ask the factory for a capacity hold without knowing the actual buy quantities. They commit to a number. Two weeks later, the buy comes in 30% higher. Now you are negotiating MOQs and air freight under deadline pressure that did not need to exist.
RFQ history lives in email threads
Last season's quote from the same vendor for a similar style is in someone's inbox — or gone. There is no system memory of which factory quoted what, when, or why the choice was made. Every season starts from zero.
Sustainability and compliance arrive late
A late-stage compliance ask — recycled content, audit certification, country-of-origin shift — forces re-sourcing under deadline. The vendor that fits the plan does not fit the requirement; the vendor that fits the requirement does not fit the calendar.
Built for sourcing as a connected planning function.
The six fields every vendor record carries — automatically.
Sourcing decisions live or die on the data attached to the vendor record. RetailNorthstar makes these first-class fields — not freeform notes in a spreadsheet.
| Dimension | How RetailNorthstar Handles It |
|---|---|
| Capacity | Monthly factory capacity vs. planned units; flags when allocations exceed available capacity. |
| Lead time | Standard, peak-season, and rush lead times by vendor; auto-checks against the in-store date on the plan. |
| MOQ | Minimum order quantity at style, color, and total levels; visible during assortment build, not at PO cut. |
| IMU contribution | Cost roll-up against IMU target by vendor; identifies margin-eroding sourcing decisions. |
| Compliance status | Audit certifications, country of origin, recycled content flags — filterable during vendor selection. |
| Performance history | On-time delivery, quality flags, post-PO change frequency — visible before the next allocation, not in a vendor scorecard built once a year. |
Questions from sourcing teams
How does this work alongside our PLM and costing tools?
RetailNorthstar is the planning and sourcing-decision layer; PLM stays the source of truth for tech packs, BOMs, and sample management. Style records sync from PLM into RetailNorthstar so sourcing decisions happen against the same product data the design team is working with. Costing tools that produce landed cost calculations integrate via API — RetailNorthstar consumes the cost output and rolls it up against IMU targets. We do not replace your costing engine; we connect its output to the merchandising plan.
Can sourcing teams use this without merchandising being on the platform?
Technically yes, but the value is muted. The reason sourcing benefits is that buy quantities flow from the assortment plan and IMU targets are visible during costing. If merchandising is still on spreadsheets, sourcing gets a vendor directory and RFQ history — but not the integrated demand signal. Most teams roll out merchandising and sourcing together; the connected workflow is where the time savings come from.
How are MOQs and capacity holds handled when the plan changes?
The platform tracks committed quantities by vendor and surfaces a re-evaluation flag when the underlying buy plan moves outside a configurable threshold (default 15%). Sourcing sees the flag with the delta and can decide whether to renegotiate, absorb, or split the difference. Capacity holds with vendors are tracked the same way — the vendor record shows what is held, what is committed, and what is at risk if the plan shifts further.
Sourcing decisions deserve the planning context.
See how RetailNorthstar connects buy quantities, MOQs, IMU targets, and vendor history — so sourcing negotiates from the plan, not against it.
Connected apparel planning — live in weeks, not quarters.