Early-access requests open

MAPPINGS AND REFERENCE DATA

Your reference data.
Ready to work together.

Keep customer codes, supplier mappings and reference tables in a private workspace your team can maintain. Check a proposed change, release an approved version and give authorised systems a consistent source.

Request early access Explore the workflow

No payment. Start with your workflow.

MAPPING CHANGE EXAMPLEConfigSheets

CS / EXAMPLE 01

Supplier option codes

Version to inspect

Example lookup resultsCurrent example

Left handSupplier control-side value

LEFT

Right handSupplier control-side value

RIGHT

Standard finishSupplier finish code, leading zeros retained

0012

The current example maps control-side options to LEFT and RIGHT. Released values remain identifiable.

Illustrative data only. No live table is being edited or released.

Compare versions. The original values remain visible.

BUILT AROUND YOUR KNOWLEDGE

For teams maintaining the tables between ecommerce, manufacturing systems and factory-floor applications.

FROM KNOWLEDGE TO A WORKING PROCESS

A small table change can reach a long way.

A renamed option or changed supplier code can affect orders, labels and integrations. ConfigSheets makes the proposed change visible and gives you a way to check it before other systems adopt it.

Bring the reference data

Start with one mapping or lookup table. Define its columns, identifiers and the system responsible for its meaning.

Review a proposed change

Compare additions, edits and removals. Check representative inputs against the results your team expects.

Release for adoption

Make an approved version available to connected applications, with explicit adoption and a history of the data used.

THE SERVICE

Maintain the table. Check the change. Release a version.

A familiar table workspace

Maintain structured rows and columns without turning each code change into an application deployment.

Mappings with clear meaning

Relate customer, supplier and internal identifiers while preserving exact values, including leading zeros.

Checks before release

Identify missing values and conflicting matches, then review examples against independently expected results.

Visible change history

See what changed and retain earlier released versions for investigation and historical reproduction.

AI assistance with review

Use SmartFACT to help prepare supported mappings and edits. People review the proposal before release.

Private data, controlled access

Keep your reference data private to your organisation. Share approved versions with the people and connected applications you authorise.

SMARTFACT, WITH HUMAN REVIEW

Describe the change. Keep the decision.

SmartFACT can help prepare a mapping proposal from your instructions and declared fields. You inspect the values, check examples and approve the result. A helpful suggestion does not silently become production data.

How configuration works

EXAMPLE CONDITION

“Map the ecommerce option “Left hand” to the supplier value “LH” for this product family.”

DraftReviewRelease

Approved content. Known fields. A version you can return to.

IS IT A FIT?

Start with one
clear workflow.

A good starting point

You maintain customer, supplier or application mapping tables.
Someone can identify the authoritative values and approve changes.
You want repeatable checks before connected systems adopt a new version.

The initial scope

Start with one defined table and an agreed consuming application.
Each dataset retains a named owner and an explicit source of truth.
Stock transactions, product calculations and order routing execution stay in their applications.

Read the service guide →

BEFORE YOU START

A few useful answers.

How does early access work?

Tell us about one workflow you want to improve. We review the fit, agree an evaluation and confirm the supported scope and onboarding arrangements with you. Requesting access is free and does not create an instant production account.

What will it cost?

Pricing, implementation work and support arrangements are agreed before you commit. There is no payment to make through this website.

Does releasing a version make our data public?

No. Releasing a version makes it available to the people and connected applications your organisation authorises. It does not create a public dataset. Each consuming application still chooses when to adopt an approved version.

Is this another spreadsheet application?

ConfigSheets focuses on structured reference data used by software: exact identifiers, predictable lookups, reviewed changes and released versions. It is not intended to replace every workbook or become your accounting system.

Will an edit immediately change every connected application?

No. The intended workflow separates drafting, releasing and consumer adoption. A production application uses an identified approved version, rather than silently following every edit.

Can it help with EDI mappings?

Yes. Customer and supplier code mappings are a starting use case. XML and API transformation execution belongs to the integration; ConfigSheets maintains and releases the agreed data it uses.

Does it replace our ERP product catalogue?

Your ERP can remain authoritative. ConfigSheets can maintain supplementary mappings or a reviewed extract. Ownership and synchronisation are agreed for each dataset.

A PRACTICAL STARTING POINT