Stop rebuilding
product specs by hand.
Turn item data, recipes, approvals, labels, PDFs, and customer spreadsheets into a controlled spec.
Inventory source
Item + recipe data
Finished Good SKU-24993
QA approval
Snapshot frozen
Approved outputs
Generated together
1 product / 5 files
Spec sheet. Label. Customer spreadsheet. Recipe calculator. Item master. The files do not share one current value.
Can we send this version to the customer?
Did the carton label get the same shelf life?
Who changed the ingredient weights?
Which spec did we print from?
The risk is not creating the spec. The risk is keeping every downstream output current after one ingredient, label, or customer template changes.
File drift
The PDF, label, and workbook get edited separately. The team loses track of which one reflects the approved product.
Manual nutrition handoffs
Recipe weights and nutrition values live outside the item record, so every formula change creates another copy step.
Weak approval trail
When a customer asks what was approved last month, the answer should be a frozen record, not a folder search.
The Product Flow
One review turns operational data into approved documents
Instead of copying values between tools, the team follows a visible path from inventory data to frozen approval to publishable output.
Inventory source
Item + recipe data
Finished Good SKU-24993
Shelf life, storage, article number, customer-ready name
Recipe / BOM
rollup-readyQA checkpoint
Approve once
The review freezes the exact product data that every downstream document will use.
Submitted
Ready for QA
Approved
Snapshot frozen
Effective
Outputs unlocked
Approved outputs
Generated from snapshot
Spec sheet PDF
Customer and audit copy
Carton label
Print-ready production label
Customer workbook
Template cells filled
If the product changes later, the published version stays explainable and the next revision goes back through review.
Before
Five separate files
During
One visible QA checkpoint
After
Every output says the same thing
The Controlled Source
One approved version for every document
QA approves the product once. Batchtab uses that same approved snapshot for compliance documents, labels, and customer-specific exports.
Versioned specifications
Draft, submit, approve, reject, and revise without overwriting the version customers already received.
Audit-ready approvals
Approval freezes the exact item fields and payload used for the published spec, even if the item changes later.
Spec-sheet PDFs
Generate a clean specification sheet from the current approved version for customers, audits, and internal QA.
Carton labels
Print carton labels from approved data, including shelf-life, storage, ingredient, and batch-facing fields where required.
Customer listing exports
Fill customer workbook templates from the approved spec instead of retyping values into spreadsheet cells.
Nutrition from recipes
Rebuild derived values from ingredient and component weights, so recipe changes flow into QA review.
Content Modules
Built for regulated products without making Batchtab food-only
Food-specific fields such as nutrition and LMIV label data live in the food module. The approval workflow, versioning, exports, and audit trail stay reusable for other specification types.
Versioning, approval, PDFs, labels, exports
Nutrition, allergens, storage, label fields
New regulated data without rewriting the workflow
How It Works
From item data to customer-ready output
The user flow is simple: build the spec from inventory, review it, approve it, then publish from the approved version.
Item
Start from inventory
Master data and module fields
Build
Pull from BOM
Weights and derived values
Review
Submit for QA
Tracked approval history
Freeze
Approve version
Output data is locked
Output
Print and export
PDF, label, XLSX
Draft
Controlled editing
The draft can change while QA is working. The approved record cannot silently drift.
Approve
Approval trail
Submitted
QA review requested
Approved
Snapshot materialized
Effective
Outputs unlocked
Submissions, approvals, rejections, and future withdrawals remain visible as history instead of disappearing into a status field.
Publish
Outputs from source
Operators print or export the approved version instead of rebuilding the same data in three tools.
Revision means a new version, not a silent overwrite
Ingredient changes, shelf-life changes, or customer-facing edits create a reviewable path back through QA. The approved record remains explainable.
No separate specification database to babysit
Specifications read from the item catalog, component structure, batches, and production-facing shelf-life data. The operational data that runs the floor also supports customer-facing documents.
SKU, name, storage, shelf-life, module data
Ingredient weights rebuild derived values
Outputs generated from the same snapshot
Keep the customer's workbook format. Stop filling it by hand.
Batchtab writes approved specification values into the cells each customer expects. Reference sheets stay in the workbook, while stale product sheets are left out of the export.
Specs beside inventory
Approve the spec, label, and customer workbook
customers see
Specs, labels, customer workbooks, and approval history. Specs sit beside inventory.
Versioning
Snapshots
Labels
Exports
Batchtab is in closed beta, with access limited to a small number of companies. Contact us to discuss whether it fits your needs.