Industry solution

FMCG & Consumer Goods

From ingredient lot to store shelf to remittance, one connected operation

For packaged food, personal care and home care: batch release, distributor stock, trade deductions, artwork and packaging EPR returns.

Products
8
Challenges
6
Concepts
15
Talk to us about Consumer GoodsAsk a question
Filling line of unbranded bottles with a quality technician holding a tablet beside tagged pallets ready for dispatch
ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)Kadaikodi(opens Kadaikodi in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)Botlit(opens Botlit in a new tab)ArtistryBase(opens ArtistryBase in a new tab)EcoImpactHub(opens EcoImpactHub in a new tab)

The problem

Why running a consumer goods brand is hard right now

Consumer goods brands release batches against retailer shelf-life rules they track by hand, sell through distributors they cannot see into, and settle promotions, artwork changes and extended producer responsibility (EPR) returns from spreadsheets.

A mid-sized consumer goods brand runs on thin margins and many hand-offs. Plants and contract packers make batches against a forecast; quality holds them until micro, seal or fill checks clear; logistics ships them to distributors and to retailer distribution centers that each set their own rules on remaining shelf life and delivery windows. Distributors sell on to thousands of outlets the brand rarely sees directly, so what the company knows best is what it billed, not what sold.

Money leaks out at the seams. Retailers settle promotions, shortages and on-time-in-full fines by deducting them from payments, and each line has to be checked against an agreement and a proof of delivery before a dispute window closes. Artwork and claims change with new regulations, reformulations and marketing, and every change touches printed packaging already in the warehouse. Packaging itself now carries reporting duties, with tonnage by material, recycled content and emissions requested by regulators and by the retailers you sell to.

Each of these lives in a different tool or spreadsheet, owned by a different team. The enterprise resource planning (ERP) system knows invoices, the plant knows batches, the distributor knows outlets, the design agency knows artwork and the sustainability lead keeps a workbook. When something goes wrong, such as a supplier notice about an ingredient lot, the brand spends its first hours finding out where things are rather than acting.

Who this is for

  • Chief operating officer

    One honest picture across plants, distributors and retailers, so service misses, write-offs and deductions stop surprising the monthly review.

  • Quality and regulatory manager

    Releasing batches on evidence, tracing any ingredient lot without rebuilding the list by hand, and keeping every pack claim tied to its substantiation.

  • Head of sales and distribution

    Seeing outlet orders and distributor stock by SKU every week, not just what was billed to distributors at month-end.

  • Trade finance and revenue manager

    Matching retailer deductions to promotion agreements and delivery proof before dispute windows close, and knowing which events paid back.

  • Supply chain and logistics manager

    Shipping released stock only to customers whose shelf-life rules it meets, and holding suspect pallets wherever they sit.

  • Packaging and sustainability lead

    Artwork changes that phase in without scrapping old labels, and packaging tonnage and recycled content that trace to real SKUs.

A day in the life

The story behind the solution

One week at a personal care and home care brand

Nadia Rahman runs operations at Harlow Hill, a mid-sized brand whose body wash, shampoo, hair oil and dishwash liquid are made in two plants and at a contract packer, sold through 48 distributors to neighborhood stores and shipped directly to two retail chains. Her week is typical: nothing dramatic on its own, but every problem crosses at least three teams, and most of her time goes on finding out where things stand.

  1. Monday, 7:40 a.m.

    A batch on hold and a retailer's shelf-life rule

    Quality manager Tomás Aguilar reports that citrus body wash batch B26-3321, made last Friday, is still waiting on its microbiology result, due Thursday morning. Logistics had planned to ship it to Crestway Grocers' distribution center on Thursday afternoon, and Crestway refuses anything with less than two-thirds of its shelf life left. The only released body wash in the warehouse is batch B25-4486 from last November, with just over half its life remaining: it would make the date but not the rule. Nobody can say, from one screen, which batches are released, how much life each has left and which orders each one can go to.

    How this is solved: Batches on quality hold while the shelf-life clock runs

  2. Tuesday, 10:15 a.m.

    Billing on plan, outlets out of stock

    At the weekly sales review, billing to distributors is on plan for the quarter. Then regional manager Ifeoma Chukwu shares field photos: the 200 ml body wash is missing from shelves across the north, while Thornvale Distributors is sitting on months of 1 liter dishwash, some of it close to expiry. The sales team sees only what Harlow Hill invoiced, and the distributor's stock report arrives as a monthly spreadsheet.

    How this is solved: Billing on plan while outlets run out of stock

  3. Wednesday, 2:30 p.m.

    A short payment with 186 deduction lines

    Crestway's payment arrives short. Receivables analyst Daniel Osei opens a remittance with 186 deduction lines: feature and display allowances from the spring promotion, a scan-based rebate, shortage claims, damaged cases and on-time-in-full fines. Each has to be matched to a promotion agreement or a delivery record before Crestway's dispute window closes. Meanwhile the key account manager asks what nobody can answer yet: did the spring promotion sell more, or did stores just stock up early?

    How this is solved: Promotions settled from a pile of retailer deductions

  4. Thursday, 11:00 a.m.

    One claim change across nine pack designs

    Marketing wants a new 30 percent recycled plastic claim on the body wash and shampoo bottles, and the fragrance supplier's reformulation changes the ingredient list on the same products. Packaging lead Mei Lin Tan counts nine artwork files: two body wash sizes and one shampoo, across three markets. Approvals are running through email threads between brand, regulatory, the packaging technologist and the printer, and the warehouse still holds tens of thousands of labels printed with the old ingredient list.

    How this is solved: One claim change, nine pack designs and old labels in stock

  5. Friday, 9:00 a.m.

    The packaging return is due and the workbook is wrong

    Sustainability lead Arjun Nair has to file the half-year extended producer responsibility return and answer a retail chain's packaging questionnaire. His workbook multiplies pack weights by units sold, but three SKUs have no weight on file, two resin certificates have expired and the unit counts came from invoices rather than shipments by market. He spends the morning reconciling instead of reporting.

    How this is solved: Packaging EPR returns and emissions built from a workbook

  6. Friday, 4:40 p.m.

    A supplier notice about two ingredient lots

    Just before the weekend, the thickener supplier emails a notice: two lots delivered last month showed a residue above the agreed limit in their own retest. Tomás needs to know which Harlow Hill batches used those lots, at which plant or at the contract packer, where the finished goods are now, which distributors received them and whether any reached outlets. The consumer careline opens on Saturday morning, and its team has no batch list to answer from.

    How this is solved: Suspect ingredient lots already out with distributors and outlets

None of this is unusual for a consumer goods brand. What changes when the products work together is how quickly each problem reaches the person who can act on it, with the record they need already attached. This story is illustrative: the organization, people and events are fictional, and the capabilities described are design intent.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Batches on quality hold while the shelf-life clock runs

ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

In personal care, home care and packaged food, a finished batch waits on quality release: micro results, seal or fill checks, a deviation to close. Each retailer distribution center sets its own minimum remaining shelf life at receipt, so a hold that misses a delivery slot can leave only older stock to ship, and on short-life packaged foods every day on hold eats into the life a retailer will accept. Quality assurance (QA) works from the batch record, the warehouse from a stock list and customer service from order dates, so nobody sees that the only batch meeting Crestway's rule is the one still waiting on its result. The warehouse ships an older released batch to make the date, the distribution center refuses it at the dock, and the brand pays for the return trip and the missed delivery.

What it costs

Refused deliveries, return freight, short-shipped orders and stock that ages into write-off, while QA is pushed to release faster instead of being told which results matter most.

How the products work together

Quality assurance (QA) releases or holds each batch in ManufacturedOps with the test results on one screen. FluidGrids passes each decision to MoveTheWheels, which is designed to match released batches to orders by each retailer's shelf-life rule and warn when an order depends on a batch still on hold. QA knows which result to chase first, and the warehouse stops shipping stock a retailer will refuse.

How it works — technical detail

Technical detail

ManufacturedOps is designed to put each batch's record, deviations, micro and in-process results and line clearance on one review screen, where QA releases or holds with the evidence attached. Each decision, with the batch's manufacture date and shelf life, is designed to pass to MoveTheWheels through a FluidGrids automation. MoveTheWheels is designed to keep each customer's minimum remaining shelf-life rule, allocate released batches first-expiry-first-out to the orders whose rules they meet, and flag any order that only a held batch can satisfy, with the time its result is needed. QA sees which pending result protects which order, logistics sees which batches can go where, and customer service is warned while there is still time to split or reschedule the shipment.

The outcome it is designed for

Released stock goes to the customers whose rules it meets, QA works first on the results that protect real orders, and fewer loads are refused at the distribution center dock.

The concepts behind it

Challenge 2 of 6

Billing on plan while outlets run out of stock

Kadaikodi(opens Kadaikodi in a new tab)FluidGrids(opens FluidGrids in a new tab)BigConsole(opens BigConsole in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

Most FMCG brands invoice distributors, and distributors sell on to thousands of small outlets through salespeople working a weekly beat. The brand records primary sales well and secondary sales barely at all. Quarter-end pushes load distributors with slow variants, while fast movers run out on outlet shelves and head office hears about it only from field photos or a distributor's monthly spreadsheet. Near-expiry stock builds up in distributor warehouses and comes back later as return claims, and outlets that quietly stop ordering are noticed only when a region misses its number.

What it costs

Lost sales on fast movers, bloated and aging distributor stock, expiry returns charged back to the brand, and targets managed on invoices that say little about what consumers bought.

How the products work together

Kadaikodi is designed to let distributors and field salespeople take store orders in one place, so the brand sees what actually sells to stores, not only what it billed. FluidGrids passes those orders and each distributor's stock to BigConsole every few hours. Sales leaders get one live board of stock cover, stock close to expiry and stores that stopped ordering, by region and distributor.

How it works — technical detail

Technical detail

Kadaikodi is designed to run the brand's distributor network on one ordering platform: each distributor is a merchant with its own stock, outlets order from their mapped distributor, and field salespeople take orders on a phone during beat visits, so outlet orders, fill rate and distributor stock are recorded as they happen. A FluidGrids automation is designed to carry that secondary data, with primary shipments and their batch numbers from MoveTheWheels, into a BigConsole data sink on a schedule. BigConsole then gives sales leaders one console of sell-in against sell-through, weeks of cover, near-expiry cases and outlets that have stopped ordering, by distributor and SKU, with regional filters and drill-down to the outlet. Row-level security, still in progress, is designed to let each distributor see only its own rows.

The outcome it is designed for

Fast movers are replenished before shelves empty, slow stock is moved or promoted before it expires, and quarter-end numbers reflect what consumers actually bought.

The concepts behind it

Challenge 3 of 6

Promotions settled from a pile of retailer deductions

FluidGrids(opens FluidGrids in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

Retailers rarely pay a promotion invoice. They deduct feature, display and price-reduction allowances, scan-based rebates, shortage and damage claims and on-time-in-full fines from their payments, often with a remittance that names a promotion number and little else. A receivables analyst must match each line to the trade promotion agreement, the proof of delivery and the appointment record before the retailer's dispute window closes. Valid lines sit unapplied for weeks, invalid ones are written off because the evidence is in another team's folder, and with the retailer's own weekly sales reports sitting in an inbox, trade marketing cannot tell whether an event created new volume or simply pulled orders forward.

What it costs

Cash stuck in unresolved deductions, invalid claims written off for lack of evidence, and next year's promotion calendar planned without knowing which events paid back.

How the products work together

When a retailer pays short, FluidGrids is designed to read each deduction line, match it to the promotion agreement and pull the delivery proof from MoveTheWheels, then draft disputes for an analyst to approve. It also collects each retailer's weekly sales report, so BigConsole can show open deductions and whether a promotion sold more in stores or just filled their shelves early.

How it works — technical detail

Technical detail

A FluidGrids workflow is designed to start when a retailer remittance arrives: PDF extraction reads the deduction lines, promotion lines are matched to the trade promotion agreements on file, and each shortage or fine is checked against the proof of delivery kept on the shipment in MoveTheWheels. A second, scheduled workflow collects each retailer's weekly sales report, and scan-based rebate lines are checked against it. A versioned decision rule clears matched lines, drafts a dispute with evidence attached where the delivery record contradicts a claim, and waits for an analyst's decision on anything unmatched. Both workflows end in one BigConsole data sink: a console shows open deductions by retailer, reason and age, and sets each promotion's retailer sales and shipments against the weeks before and after, showing whether stores bought ahead. An Explain panel on BigConsole's roadmap is designed to summarize those figures with citations.

The outcome it is designed for

Deductions are resolved inside the dispute window with evidence attached, valid promotion claims clear without rework, and the next calendar is planned on what each event returned.

The concepts behind it

Challenge 4 of 6

One claim change, nine pack designs and old labels in stock

ArtistryBase(opens ArtistryBase in a new tab)Botlit(opens Botlit in a new tab)ManufacturedOps(opens ManufacturedOps in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

A pack carries more than a design: the ingredient list, allergen or warning statements, net contents, barcode, recycling marks and every marketing claim, each of which must be backed by evidence and correct in every language. One change, such as a reformulated fragrance or a new recycled-content claim, touches many SKUs and markets at once. Proofs move by email between brand, regulatory, the packaging technologist and the printer; nobody is sure which version is current; and claims are checked against substantiation files on someone's drive. Meanwhile printed labels for the old version sit in the warehouse, and the new version reaches the line either too early, scrapping good stock, or too late, putting an outdated ingredient list on shelf.

What it costs

Artwork errors that can force a relabel or a withdrawal, claims that cannot be backed when a regulator or retailer asks, and printed packaging written off at every change.

How the products work together

Every pack design is designed to live in ArtistryBase in one grid of products and markets, showing the current version, what changed on the back of the pack and who has signed it off. Reviewers ask Botlit whether a claim is backed and attach its sourced answer to their note. On the final sign-off, FluidGrids tells ManufacturedOps, which uses up the old labels before the new design reaches the line.

How it works — technical detail

Technical detail

ArtistryBase is designed to lay the affected packs out as an approval matrix of SKUs by market, where brand, regulatory, the packaging technologist and the printer proof each record a sign-off, and a change view shows every panel a change touches, the back-of-pack text diff and each claim's evidence status. Reviewers ask a Botlit agent grounded in the claims substantiation files from the cell; its cited answer is designed to be attached to the review note, or to say plainly that nothing supports the claim. When the last sign-off is recorded, a FluidGrids automation is designed to pass the approved version number, the affected SKUs and markets, and the planned effective date to ManufacturedOps. ManufacturedOps then holds old-version and new-version packaging as separate material lots, consumes the old lots on scheduled production orders and releases the new version for the first order after run-out.

The outcome it is designed for

Every printed pack traces to an approved version and its evidence, claim questions get an answer with its evidence attached, and artwork changes reach the line with less packaging scrapped.

The concepts behind it

Challenge 5 of 6

Packaging EPR returns and emissions built from a workbook

EcoImpactHub(opens EcoImpactHub in a new tab)ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

Extended producer responsibility (EPR) schemes ask brands to report the packaging they place on the market by material and format, often by country or state, and to show recycled content. Retail chains send their own questionnaires on packaging emissions and recyclability. The numbers come from pack specification weights, units produced and shipped by market, and supplier certificates for recycled resin and board, and in most brands they meet only in a sustainability lead's workbook. A missing pack weight, an expired certificate or units counted from invoices instead of shipments quietly changes the obligation, and nobody can show where a figure came from when the return is questioned.

What it costs

Returns filed late or restated, recycled-content claims that cannot be evidenced, questionnaires answered inconsistently, and fees or obligations calculated on the wrong tonnage.

How the products work together

EcoImpactHub is designed to keep every pack's weights, materials and recycled-content certificates in one place. FluidGrids brings in how many units were made in ManufacturedOps and shipped to each market in MoveTheWheels. The sustainability lead sees packaging tonnage, recycled share and emissions by material, with missing weights and expired certificates flagged, and every figure traced to its source.

How it works — technical detail

Technical detail

EcoImpactHub is designed to keep a packaging ledger per SKU: component weights by material and format, recycled content backed by the supplier certificate, and an emission factor for each material. Units produced come from ManufacturedOps production orders, where packaging arrives as material lots from each supplier, and units shipped by market come from MoveTheWheels shipments, both designed to be carried in by FluidGrids automations. EcoImpactHub is then designed to compute tonnage placed on the market, recycled share and packaging emissions by material, flag any SKU with a missing weight or an expired certificate, and feed verified lines into framework-tagged reports whose figures trace back to the entries behind them. The retailer questionnaire and the regulatory return draw on the same lines, so they say the same thing.

The outcome it is designed for

Returns and retailer questionnaires draw on the same verified lines, gaps are fixed before filing, and every tonnage figure traces to the SKUs and shipments behind it.

The concepts behind it

Challenge 6 of 6

Suspect ingredient lots already out with distributors and outlets

ManufacturedOps(opens ManufacturedOps in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)Kadaikodi(opens Kadaikodi in a new tab)Botlit(opens Botlit in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

Ingredient suppliers do send notices: a lot retested above an agreed limit, a mislabeled drum, a certificate of analysis issued in error. The brand must then find every batch that consumed those lots, across its own plants and a contract packer, and every place the finished goods now sit: plant stores, a third-party warehouse, trucks on the road, distributor warehouses and outlets. Consumption is on batch sheets, stock is in the warehouse system and distributor deliveries are in the distributor's own books. The first day goes on building the list, while stock keeps moving and the careline takes calls it cannot answer.

What it costs

Suspect stock keeps shipping while the scope is built, holds end up broader and costlier than needed, and consumers and retailers get slow or inconsistent answers.

How the products work together

ManufacturedOps is designed to trace the suspect supplier lots to every batch that used them. FluidGrids passes that list to MoveTheWheels, which stops those pallets moving and flags trucks on the road, then to Kadaikodi, which flags that stock at distributors and lists the stores that bought it. A Botlit careline assistant is designed to answer by batch code and pass anything about a reaction or injury to quality staff.

How it works — technical detail

Technical detail

ManufacturedOps genealogy is designed to trace the supplier lots forward to every batch that consumed them, at either plant or the contract packer, and to the finished-goods lots each batch produced. A FluidGrids automation is designed to pass that scope to MoveTheWheels, where a quality hold blocks allocation and picking in every warehouse, flags loads in transit for intercept and lists delivered primary orders with their batch numbers. The same automation passes that delivery list to Kadaikodi, which is designed to flag the matching distributor stock so it is not sold on and to list the outlets that ordered from those deliveries. The batch list and approved holding statement go into the knowledge base of a Botlit careline agent on WhatsApp, designed to answer by batch code from that wording, cite it, and hand anything about a reaction or injury to the quality team. Holds are designed to be released lot by lot when quality signs off.

The outcome it is designed for

The scope is known before the weekend starts, suspect stock stops moving in warehouses and at distributors, and the careline opens on Saturday with one approved answer for every batch code.

The concepts behind it

How it fits together

How it fits together across one brand week

Follow one loop through a brand's week: what stores ordered, the questions it raised, the pack change that followed, the next batch, its shipment and the packaging return. Each step is one product doing its part, designed to hand a concrete record to the next.

  1. To BigConsole: store sales and stock cover for each distributor

  2. To Botlit: the live figures an assistant can look up

  3. To ArtistryBase: the evidence behind a pack claim

  4. To ManufacturedOps: the approved pack design and the date it takes effect

  5. To FluidGrids: which batches are released, and how much life each has

  6. To MoveTheWheels: released batches and any stock that must stay put

  7. To EcoImpactHub: how many units went to each market

Step 1 of 8: Take outlet orders

How each hand-off works — technical detail

Technical detail

  1. 1. Kadaikodi — Take outlet orders: Is designed to record distributor stock and the outlet orders salespeople take on beat visits, building a secondary sales record by outlet and SKU.Hands to BigConsole: Secondary sales, fill rate and weeks of cover by distributor, through a FluidGrids data sink
  2. 2. BigConsole — Read sell-through: Shows sell-in against sell-through, retailer sales around each promotion and open deductions on live consoles with filters and drill-down.Hands to Botlit: Live figures a Botlit agent can look up when a manager asks
  3. 3. Botlit — Answer from approved sources: Can look up BigConsole figures, and is designed to answer claim questions from the substantiation files with citations and hand exceptions to people.Hands to ArtistryBase: Cited claim evidence, designed to be attached to the pack's review note
  4. 4. ArtistryBase — Approve the pack change: Is designed to show every pack a change touches, the back-of-pack text diff and a recorded sign-off from each approver.Hands to ManufacturedOps: Approved version, affected SKUs and markets, and effective date, carried by a FluidGrids automation
  5. 5. ManufacturedOps — Release batches, phase in labels: Is designed to release or hold each batch with its test results, and to use up old-label lots before the new version reaches the line.Hands to FluidGrids: Release decision with batch number, manufacture date and shelf life, plus units made
  6. 6. FluidGrids — Pass the decision on: Is designed to route release decisions and hold scopes to MoveTheWheels, and to carry units made and shipped to EcoImpactHub on a schedule.Hands to MoveTheWheels: Released batches and any hold scope, lot by lot
  7. 7. MoveTheWheels — Allocate by shelf life: Is designed to allocate released batches by each customer's minimum shelf-life rule, ship them and keep the proof of delivery on the shipment.Hands to EcoImpactHub: Units shipped by market, carried in by a FluidGrids automation
  8. 8. EcoImpactHub — Report the packaging: Is designed to combine pack weights and supplier certificates with units made and shipped by market into tonnage, recycled share and emissions by material.

Products in this solution

What each product brings

  • ManufacturedOps

    Batch release, genealogy and packaging lots

    Keeps the plant record: what was made, which ingredients and packaging went into each batch, the checks it passed and whether it is on hold. Tracing batches back to their ingredients is being built.

    Technical detail

    Technical detail

    A manufacturing execution system: production orders with hold states, inspections, non-conformance and material disposition, and material lots with status; forward and backward genealogy is being built, and QA batch release with shelf-life data is designed here as an extension.

    Visit ManufacturedOpsAll concepts

  • MoveTheWheels

    Warehouses, shelf-life allocation and delivery proof

    Keeps track of warehouse stock, shipments and delivery paperwork. It is designed to follow batch numbers, so released stock goes to customers whose shelf-life rules it meets and suspect stock can be stopped anywhere.

    Technical detail

    Technical detail

    Tracks warehouse stock, orders, shipments and delivery documents on one record, and is designed to carry batch numbers, so released stock is allocated by shelf-life rule and suspect lots are held wherever they sit.

    Visit MoveTheWheelsAll concepts

  • Kadaikodi

    Distributor and outlet ordering

    Gives distributors and field salespeople one place to take store orders and manage stock, so the brand can see what actually sells to stores, not only what it invoiced.

    Technical detail

    Technical detail

    A multi-merchant commerce platform with catalog, stock, orders and field worker tasks, designed here to run distributors as merchants and capture outlet orders, so secondary sales are recorded as they happen.

    Visit KadaikodiAll concepts

  • FluidGrids

    Automation that moves records between products

    Automations you draw on screen are designed to pass release decisions, hold lists and retailer deductions between products. Its built-in link sends figures to BigConsole boards.

    Technical detail

    Technical detail

    Visual workflows with PDF extraction, branching rules and waits are designed to route releases, hold scopes and deductions, pausing for an analyst's decision; its built-in Burdenoff link is the BigConsole data sink node that feeds live consoles.

    Visit FluidGridsAll concepts

  • BigConsole

    Sell-through and deductions consoles

    Gives sales and finance leaders live boards of sales to stores, distributor stock, retailer sales around promotions and open deductions. Showing each distributor only its own figures is still being built.

    Technical detail

    Technical detail

    Live consoles with filters and drill-down read data sinks fed by FluidGrids workflows; row-level security, which would show each distributor only its own rows, is in progress, and a cited Explain panel is on the roadmap.

    Visit BigConsoleAll concepts

  • Botlit

    Cited answers for claims and the careline

    Assistants are designed to answer from the brand's approved documents, show where each answer came from and pass hard cases to people, on WhatsApp or team chat. They can look up BigConsole figures and start FluidGrids automations.

    Technical detail

    Technical detail

    Agents are designed to answer from the brand's own knowledge bases with citations, on WhatsApp and team channels (a web chat widget is on its roadmap), and to hand anything they cannot answer to a person; they can query BigConsole dashboards and trigger FluidGrids workflows.

    Visit BotlitAll concepts

  • ArtistryBase

    Pack artwork versions and sign-offs

    Keeps every version of every pack design, with review notes pinned to the exact spot and a record of who approved what. It is designed to show everything a pack change touches.

    Technical detail

    Technical detail

    Keeps every artwork version immutable, with review notes pinned to the exact region and explicit sign-offs per approver, designed here as a SKU-by-market approval matrix and a change view for packs and their claims.

    Visit ArtistryBaseAll concepts

  • EcoImpactHub

    Packaging ledger, emissions and reports

    Keeps emissions records with their sources and builds reports for common frameworks. For packaging, it is designed to track pack weights, recycled content and tonnage by material for producer responsibility returns.

    Technical detail

    Technical detail

    A carbon ledger across Scopes 1 to 3 with sourced emission factors and framework-tagged reports, designed here to add a packaging ledger of weights, recycled content and tonnage placed on the market.

    Visit EcoImpactHubAll concepts

One platform underneath: Burdenoff Workspaces

Every product here runs on Burdenoff Workspaces: one sign-on for plant, sales, finance and packaging teams, role-based access designed to limit distributors and contract packers to their own records, one audit trail across releases, holds, approvals and disputes, and one bill.

Concept gallery

Every concept in this solution

15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Consumer Goods solution in one minute

A consumer goods brand loses margin at the seams: a batch released too late for a retailer's shelf-life rule, a distributor overstocked on the wrong variant, a deduction written off for lack of a delivery record, a label printed with last year's claim. Burdenoff brings ManufacturedOps, MoveTheWheels, Kadaikodi, ArtistryBase and EcoImpactHub together, connected by FluidGrids and read through BigConsole and Botlit, so each moment is designed to reach the right person with the evidence attached.

  • Batch release decisions are designed to drive allocation by each retailer's shelf-life rule, before a load is refused at the dock.
  • Distributor stock and outlet orders are designed to reach one live sell-through console, by region, distributor and SKU.
  • Retailer deductions are designed to be matched to promotion agreements, delivery proof and retailer sales, with disputes drafted for approval.
  • Pack changes are designed to carry recorded sign-offs and cited evidence, with old labels used up before the new version reaches the line.
  • A supplier notice about an ingredient lot is designed to become a lot-by-lot hold in warehouses and at distributors, and one approved careline answer.
Email it

Questions

Frequently asked

Do we have to replace our ERP or our distributors' systems?

No. Your enterprise resource planning (ERP) system stays the home for invoices, prices and finance. ManufacturedOps is designed to share orders and stock with your ERP, and that link is on its roadmap. Distributors without a system can take store orders in Kadaikodi, and FluidGrids is designed to collect regular reports from those who already have one.

Technical detail

Technical detail

No. The products are designed to sit beside the ERP, which stays the record for invoices, pricing and finance. ManufacturedOps offers a GraphQL API and is designed to exchange orders, bills of materials and inventory with the ERP; two-way ERP sync is on its roadmap. Kadaikodi is designed to take outlet ordering for distributors who have no system of their own, and FluidGrids is designed to collect scheduled exports from distributors and retailers who already have one.

Can distributors and contract packers use it without seeing each other's data?

Yes, that is the intent. Access is set by role, so each distributor or contract packer can be limited to its own orders, stock or batches. BigConsole's option to show each distributor only its own figures on a shared board is still being built. Every access change and approval is recorded.

Technical detail

Technical detail

That is the design intent. Everything runs in Burdenoff Workspaces with role-based access enforced at the gateway, so a distributor or a contract packer can be limited to its own orders, stock or batches. BigConsole's row-level security, which is designed to scope a shared console to each distributor's rows, is in progress. Access changes and approvals are recorded in one audit trail.

Does this make our pack claims or labels compliant?

No. The products do not give legal or regulatory advice or certify claims. They are designed to keep a record of which version each person approved and which evidence backed each claim. Your own regulatory and legal reviewers still decide.

Technical detail

Technical detail

No. The products do not give regulatory or legal advice and do not certify claims. ArtistryBase is designed to record which version each approver signed and which evidence stood behind each claim, and a Botlit agent is designed to answer only from the substantiation files you load, citing them and saying so when nothing matches. Your regulatory and legal reviewers still make the decision.

Can the careline assistant handle complaints about reactions or injuries?

No. The assistant is designed to answer routine questions, such as whether a batch code is affected, only from the approved statement. Anything about a reaction, injury or foreign object is designed to go straight to your quality or consumer team with the conversation attached.

Technical detail

Technical detail

It is designed not to. A Botlit careline agent is designed to answer routine questions, such as whether a batch code is affected, only from the approved statement and batch list, with the source cited. Any message that mentions a reaction, an injury or a foreign object is designed to go to the quality or consumer affairs team with the conversation attached, and the agent says plainly when it has no approved answer.

Is the packaging ledger an official EPR filing tool?

No. EcoImpactHub is not a regulator or compliance scheme. It is designed to keep the evidence behind your producer responsibility return, such as pack weights, units shipped and recycled-content certificates, so you file through your market's own system and can show how every figure was reached.

Technical detail

Technical detail

No. EcoImpactHub is not a regulator or a compliance scheme. It is designed to hold the evidence behind a return: pack weights by material, units shipped by market, recycled-content certificates and emission factors, each line traceable to its source. The return itself is filed through the scheme or portal your market requires, using figures you can show the working for.

Is any of this live today?

Partly. The products are early, and this page describes a solution concept. Some pieces exist today, such as production and lot records, automations and live boards. Batch tracing and assistants that show their sources are being built, and the industry screens here are designed concepts.

Technical detail

Technical detail

Burdenoff products are pre-launch or early, and this page describes a solution concept. Some building blocks exist today, such as ManufacturedOps production orders, inspections and material lots, FluidGrids workflows, and BigConsole consoles with filters. Lot genealogy, cited assistant answers and scheduled data feeds into BigConsole are being built. The industry-specific surfaces shown here, including shelf-life allocation, deduction matching, the distributor board, the pack change view and the packaging ledger, are designed concepts. We can walk through what exists and what is on each roadmap.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.