1
Finished goods are created in CocoaCraft
A maker completes a production run, records actual output, and moves finished product into inventory after the workflow step they choose.
Back to roadmap
Future Module / Under Review
Shopify Inventory & Production Sync
This future module would connect CocoaCraft production records with a maker's Shopify store so finished goods can update sellable inventory, sales demand can flow back into production planning, and reorder points can trigger the next batch before stock runs out.
The goal is not to replace Shopify. Shopify remains the storefront and checkout system. CocoaCraft becomes the production, inventory, quality, and traceability layer that helps makers know what they made, what is sellable, and what needs to be produced next.
Workflow concept
From finished batch to sales demand
2
The maker controls what counts as sellable
CocoaCraft can recommend syncing only released inventory, but each maker can decide whether Shopify should receive completed, packaged, released, manually approved, or allocated inventory.
3
Sellable quantity can update Shopify
When a product is mapped to a Shopify variant, CocoaCraft can push the calculated sellable quantity to the connected Shopify account.
4
Shopify demand comes back into CocoaCraft
Shopify sales, order activity, and inventory changes can be recorded in Supabase so CocoaCraft can understand demand without replacing Shopify checkout.
5
Low stock can trigger production planning
When Shopify inventory or CocoaCraft sellable inventory reaches a maker-defined threshold, the system can recommend a reorder, draft a production run, or flag ingredient shortages.
Maker-controlled sync
Recommended defaults, flexible execution
CocoaCraft can recommend a quality-minded default, but makers should be able to configure how their shop works. A tiny maker may treat completed product as sellable. A more formal operation may require packaging, review, release, or channel allocation before Shopify inventory is updated.
Released inventory only
Recommended default. Only finished goods that are completed, reviewed, and released for sale are pushed to Shopify.
Completed production inventory
Inventory can be counted once a production run is completed, useful for very small makers with simple workflows.
Packaged inventory only
Inventory does not sync until product has been wrapped, labeled, or otherwise prepared for sale.
Manual approval before sync
CocoaCraft calculates the available quantity, but the maker must approve the Shopify update before it is pushed.
Channel allocation
Future support for splitting inventory across Shopify, wholesale, markets, samples, internal use, or other sales channels.
No auto-sync
CocoaCraft tracks production and finished goods internally while Shopify updates remain manual.
Shopify remains the commerce system
Shopify continues to own storefront listings, checkout, payments, customer orders, and public selling inventory.
CocoaCraft remains the production system
CocoaCraft owns formulations, production runs, finished goods lots, batch history, quality status, and traceability records.
Supabase acts as record and sync layer
Supabase stores CocoaCraft production data, Shopify mapping records, webhook events, sync status, reorder settings, and exception history.
Why this matters
This turns production history into operational planning.
The value is not just syncing a number to Shopify. The bigger value is connecting sales demand, finished goods, formulas, ingredient availability, quality status, and production planning into one workflow. That helps makers decide what to make next, whether they have enough ingredients, and when stock is at risk before it becomes a customer problem.