SmartFACT DataConfig sheets, kept in order

HOW IT WORKS · UPDATED 20 OCTOBER 2026

Bringing your data into SmartFACT

Bringing data into a factory system means getting orders, codes and reference values from where they are kept today into the software that uses them, without retyping. In SmartFACT, data comes in through each product’s own import or through SmartFACT Data at data.smartfact.ai, which adds maintained tables, the WooCommerce shop connector and integrations with other systems that we build for you.

Two routes in

RouteBest for
A product’s own importData only that product uses, in the format it already accepts
SmartFACT Data tablesCodes and lookup values that several products or people rely on, with checked changes and saved versions
WooCommerce connectorShop orders that should reach StoresFlow stock without retyping
An integration built for youSAP, ERP and MRP systems, other software, EDI, a live Google Sheet or a bespoke API

Products keep their own imports. SmartFACT Data is the route for data that is shared, needs a change history or comes from another system.

Maintained tables

Paste rows from your spreadsheet with their header row, or enter them in the grid, then review and save. Each table keeps every saved version, and the receiving product takes data from the version you choose. Versioned reference tables covers the detail.

Shop orders

The WooCommerce connector reads orders through a read-only key, maps each shop SKU to a stock item through a reviewed mapping and hands the result to StoresFlow. See WooCommerce orders into StoresFlow.

Other systems, connected for you

SAP, ERP and MRP systems, other software, EDI and bespoke APIs are connected as a paid integration that we scope with you and build through data.smartfact.ai. The data then reaches the receiving product the same way as a maintained table: from a saved version, with the receiving product’s own review.

Getting started

Start with one table that several people rely on, or with your shop orders. Bring a small synthetic example rather than real values:

  • Column names and what each value means.
  • Examples with leading zeros, blanks and changed codes.
  • The receiving SmartFACT product and the data it needs.
  • Who maintains the table and who checks the receiving file.

We agree the scope and authorise users through SmartFACT Accounts. Your owner sets up the table, checks a first saved version and rehearses the receiving workflow before relying on it for live work.

Questions

What kinds of data can it hold?

Shop orders, customer and supplier codes, lookup values and structured inputs for the SmartFACT products you use. We define the table fields and check representative values together. SmartFACT Data is not a stock ledger or a manufacturing rules engine.

How do SmartFACT products receive the data?

A receiving product takes data from a saved version, then reviews and accepts it: LabelRules reviews a reference table before activating it, and KitProof accepts reviewed job files. Products also keep their own imports.

Read next

Is one of your config sheets a good place to start?

Tell us what the table holds, who maintains it and which product or system reads it.

Tell us about your data ↗

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.