FORGE · PRODUCT LIFECYCLE
Every style, one record,
start to finish.
Forge holds the product from first concept to sign-off, then feeds what is approved into Core and out to the channels it sells through, including Shopify.
01 · THE PRODUCT RECORD
Every style is one record, not five files.
A product in Forge carries its overview, attributes, colourways, variants and SKUs in one place, so nothing about a style lives in a separate spreadsheet or a designer's inbox. Draft through to sign-off, the record is the same one, updated rather than recreated. Yukti can start that record from an existing style or from a prompt, and once a variation is approved it becomes the draft.
One record per style.
Overview, attributes, colourways and variants held together, not split across files.
Draft to sign-off, unbroken.
The record updates in place through the whole lifecycle rather than being rebuilt at each stage.
Evolve or create with Yukti.
Describe a change to an existing style, or start from a prompt, and review what comes back.
Approved before it is written.
A Yukti draft goes through Forge Approvals as a governed action before the record is created.
02 · BUILD
Turn a concept into a spec that can be made.
Tech pack, CAD, BOM and samples sit against the same product record, so the spec a factory works from is never a step behind the design. A bill of materials is authored from the product it belongs to, not assembled afterwards from someone's notes. Fit results come from samples, recorded against the record that will carry them into production.
Tech pack on the record.
Construction, measurements and callouts held against the style they describe.
BOM authored in place.
Every bill of materials created from its own product, not built separately and attached.
Samples drive fit.
Fit status is set by recorded sample results, not edited by hand.
CAD alongside spec.
Design files sit with the construction detail they inform.
03 · MATERIALS & SOURCING
Quote it and cost it before you commit to it.
Materials, colour and palettes feed straight into sourcing, where suppliers are quoted through RFQs and a cost sheet is built before a purchase order exists. This is the quote on a new style, not the ongoing management of a supplier already shipping, which is what the buying side of Merchmix does once a style is committed. Forge answers what a style will cost to make, before it is bought.
Palettes feed the build.
Materials and colourways chosen here carry through to the tech pack and BOM.
RFQs per style.
Quotes requested from suppliers against the actual construction and materials.
A cost sheet before commitment.
Landed cost estimated before a style is bought, not after.
Suppliers by type.
Mills, cut and sew, and trim vendors held and compared in one view.
04 · YUKTI
Describe the change, review it, approve it.
Yukti evolves an existing style or starts a new one from a prompt. Say what should change, a relaxed fit, sharpened details, a lighter material, a seasonal accent colour, and Yukti proposes a variation to review rather than a finished decision. Naming, sizing and colours follow once a direction is approved. Nothing is written to the product record until the draft is approved through Forge Approvals, so creative speed does not bypass sign-off.
Evolve or start fresh.
Choose an existing style to change, or begin from a prompt with no starting point.
Directions, not blank prompts.
Suggested directions such as relax the fit or sharpen the details, or describe your own.
A shortlist of names.
Yukti proposes names for a new variation rather than leaving it unnamed.
Approval before creation.
Every draft is a governed action, reviewed and approved before the record exists.
05 · CONNECTION
Approved here, planned there, live everywhere.
A style does not stop at sign-off. What Forge approves becomes the range Core plans against, so a buy is built from styles that actually exist rather than a placeholder line waiting on development. From the same record, a product is published outward to the channels it sells through, including Shopify, so what a customer sees traces back to the record that built it.
Feeds Core.
Approved styles become the range that budget, assortment and buying plan against.
One record, published outward.
Channel content and listings are prepared from the product record itself.
Shopify included.
Products publish to Shopify from the same workflow, not a separate export.
Nothing planned twice.
What is planned in Core is what was actually approved in Forge, not a re-entered copy of it.
“That insight means fewer wasted samples, tighter edits, and collections that hit the mark more often.”
Raul Hernandez
Designer, Sydney Australia
One record, the whole way through.
Forge is not a design tool bolted onto a spreadsheet. A style is one record from first concept to sign-off, whether it started with a designer or with a Yukti prompt, and the tech pack, the cost sheet and the eventual listing all read from that same record rather than a copy of it. What Forge approves is what Core plans against, what Core Plus eventually allocates, and what a customer sees on the channels it publishes to.
Core
The range plan that Forge's approved styles feed into.
Core Plus
Allocation and replenishment for what Forge has built and Core has planned.
Horizon ERP
The ledger that purchase orders and landed costs post to.
Beacon
Where a raised purchase order reaches the supplier and comes back confirmed.
Frequently asked questions about Merchmix Forge
Bring your own range into Forge.
A six-week proof of concept on your own data, with your styles, your suppliers and your workflow.