Bring your data in
Paste rows from a spreadsheet with their header row, or enter them in the table grid. Shop orders come in through the WooCommerce connector. Column names, value types and ownership are agreed with you during onboarding.
Part of the SmartFACT suite
Your config sheets.
CONFIG SHEETS FOR MANUFACTURERS
Your config sheets.
Checked, versioned, delivered.
A config sheet is a table of reference values that other systems look up: product options, customer and supplier codes, and the lookup values behind labels, kits and orders. ConfigSheets, part of SmartFACT Data, keeps those tables in one place, checks every change before it is saved and keeps each saved version, then delivers a chosen version to the SmartFACT products that use it, or serves it to your own tool through a GraphQL API.
Bring existing tables across by pasting rows from a spreadsheet.
CS / EXAMPLE 01
Supplier reference values
Values maintained in the tableReference values
Left handControl-side lookup value
LHRight handControl-side lookup value
RHStandard finishText code preserved with its leading zeros
0012These fictional supplier values are maintained as table data. Check the saved version before preparing a supported output; the receiving product controls how it uses that output.
Illustrative values only. This example does not edit your data or send a file.
Keep clear reference values for each supported workflow.
WHO IT IS FOR
Manufacturers who keep product options, customer and supplier codes or lookup tables in spreadsheets, and need the right values to reach labels, kits, stock and the people on the floor.
ONE PLACE FOR SHARED VALUES
Stop wondering which copy has the right values.
A customer code changes. Someone updates a spreadsheet, another person keeps an older export, and the difference reaches the floor. SmartFACT Data gives your organisation one place to maintain shared tables, review each change and keep the exact version each product received.
Check and save
Review counts what is added, changed, removed and unchanged, with the values before and after. Save a new version with a note. A proposal with a problem leaves the saved version as it was.
Deliver it for review
The receiving product takes data from a saved version and keeps its own review and activation controls. LabelRules reviews a reference table before activating it, and KitProof accepts reviewed job files.
TWO WAYS TO USE IT
Inside SmartFACT, or inside your own tool.
The same checked, versioned sheets serve either route, or both at once.
Reference tables for SmartFACT products
Maintain the tables your SmartFACT products rely on and deliver a saved version to the product that uses it, which reviews it before use.
- Versioned reference tables with checked changes.
- Delivery for review to LabelRules, KitProof, StoresFlow and the other products.
- Sign-in, roles and two-factor checks through SmartFACT Accounts.
Mass configuration behind your own software
Keep the option sets, product configurations, code lists and parameter tables your own configurator or platform depends on, and let your application read them over the API.
- Your application reads reviewed, saved versions through GraphQL.
- A change is reviewed before it becomes current.
- Each credential is scoped to one workspace; editing screens can sit inside your tool.
WHAT IT KEEPS
The tables your other systems look up.
Each table has defined columns and a key, and every saved version is kept. Typical config sheets in a factory include:
Product options and codes
The code each option, finish or control side maps to, kept as text so values such as 0012 keep their leading zeros.
Customer and supplier codes
A customer’s or supplier’s code beside your own, one row per pair, so the printed code and the internal code never get mixed up.
Shop SKU mappings
Each WooCommerce SKU mapped to a stock item with the exact number of base units each sale represents, reviewed before it is used.
Inputs for kit jobs
The source tables a KitProof job file is prepared from, with every generated file kept beside the versions it came from.
REFERENCE DATA FOR YOUR WORKFLOWS
Your team supplies the data. Each product applies its rules.
SmartFACT Data maintains the values your workflows rely on. Each product decides how those values affect its work, such as a label or a kit, using its own reviewed configuration. Saving a table never silently changes production: the receiving product reviews and accepts its input first.
How data reaches a receiving productEXAMPLE REFERENCE ROW
“Supplier A. Control side: Left hand. Supplier code: LH. Finish code: 0012.”
Maintain→Check→Deliver
Reviewed output: The saved table keeps LH and 0012 exactly. A delivery takes values from that saved version; the receiving product reviews them before using them in its workflow.
BUILT FOR EXACT VALUES
The right value, and the version it came from.
Defined columns and exact codes
Give fields clear names and types. Text is kept exactly as entered, so identifiers such as 0012 keep their leading zeros, and a whole number pasted with a leading zero is refused rather than changed.
Checked changes
Review counts every added, changed, removed and unchanged row, with before and after values. Removals are confirmed explicitly, and a problem leaves the table unchanged.
Every saved version kept
Each save keeps a version with its note and author. Revisit the exact version a product received when you investigate why a label or a job differed.
No silent overwrites
Each draft records the version it started from. If someone else saves first, the older draft is refused, so their change is never overwritten.
Exact lookups
Look up a code and see every table that holds exactly that value, with the version it came from. ACME-00024 finds it; acme-00024 is a different code.
Reviewed delivery
Files are prepared from a chosen saved version with their evidence. The receiving product reviews and accepts each one; saving a table changes nothing on its own.
IS IT A FIT?
Start with one table that several people rely on.
A good starting point
- You maintain codes, lookup values or tabular inputs that change over time.
- Your team needs a clear record of changes and of the version each product received.
- Your data is in spreadsheets, in a WooCommerce shop, in a system we can connect for you, or behind a tool of your own that needs maintained configuration.
What it does not do
- It is not a stock ledger. StoresFlow keeps stock and records every movement.
- It does not decide what a label prints or how a kit is built. Rules, production activation, printing and physical work remain with the receiving product.
- It does not invent codes or values. Your team supplies and checks the data.
BEFORE YOU START
A few useful answers.
What is a config sheet?
A table of reference values that people and systems look up instead of retyping: product options and their codes, customer and supplier cross-references, and lookup values for labels, kits and orders. What is a config sheet?
Can we use it inside our own software?
Yes. ConfigSheets can sit behind your own configurator, quoting tool or platform: your team maintains and reviews the sheets, and your application reads the saved versions through a GraphQL API. Embed config sheets in your own tool.
Do we need Google Sheets?
No. Paste rows from any spreadsheet or enter them in the grid. The table does not depend on the original spreadsheet afterwards. Keeping a live Google Sheet connected is a paid integration scoped with you.
Does saving a table immediately change production?
No. Saving keeps a new table version. You prepare a supported output deliberately, and the receiving product applies its own review and activation before it uses the data.
Does saving or exporting make our data public?
No. Access is through your organisation and explicit SmartFACT Accounts permissions. A downloaded file is for your authorised workflow; you control where it is transferred.
Can it hold our EDI cross-references?
Yes. It holds the customer, partner and internal codes that a mapping depends on, with checked changes and saved versions. Connecting your EDI software or provider is a paid integration that we scope with you and build through data.smartfact.ai.
What does it cost?
See how SmartFACT Data is offered. There is no payment to make through this website.
GUIDES
Find the part you care about.
CONFIG SHEETS
What is a config sheet?
A config sheet is a table of reference values, such as product option codes or customer codes, that other systems look up. How they go wrong, and how to keep them right.
HOW SMARTFACT DATA WORKSVersioned reference tables
A versioned reference table keeps every saved version of a lookup table. See how SmartFACT Data checks each change, refuses stale edits and keeps every version.
HOW SMARTFACT DATA WORKSReviewed file transfers
A reviewed file transfer hands data to another system as a file the receiver checks first. See how SmartFACT Data prepares LabelRules and KitProof files from saved versions.
HOW SMARTFACT DATA WORKSWooCommerce orders into StoresFlow
A shop connection turns each WooCommerce order into the stock it uses. See how SmartFACT Data maps shop SKUs exactly and hands orders to StoresFlow for stock.
TWO WAYS TO USE ITData into SmartFACT
Factory data reaches SmartFACT through each product’s own import or through SmartFACT Data. Which route suits which data, and how other systems are connected.
TWO WAYS TO USE ITEmbed in your own tool
Use ConfigSheets inside your own configurator, ERP add-on or platform: maintain option sets and parameter tables at scale, and read reviewed versions through GraphQL.
CONFIG SHEETSUse cases
Where manufacturers use config sheets: customer codes on labels, supplier option codes, EDI, kit inputs, shop SKUs and configuration behind your own tool.
START WITH ONE TABLE
Which data do you need to bring in?
Tell us which data you need to bring in, where it is held today and which SmartFACT products need it. We agree a focused start with you.
Tell us about your data
Please describe the data without attaching confidential values.
THE SMARTFACT SUITE
One suite for the factory floor.
SmartFACT Data is part of SmartFACT, a set of focused services and free tools for manufacturers. People sign in through SmartFACT Accounts, with two-factor checks for the roles that approve and activate.
Other SmartFACT services print labels, check kits, guide work steps and keep stock. SmartFACT Data keeps the reference values and shop orders they rely on, and each of them reviews what it receives.
ConfigSheets also works outside the suite: embed it in your own tool and read reviewed sheets through its GraphQL API.
Explore SmartFACT