01 — Overview
The most common first app on Chamfer replaces a spreadsheet. The sheet works until it has 12 editors, three copies and no record of who changed a number. Connect it and describe the tool you want in its place: a rota, a rate card, an expense tracker. The Bench reads the headers and sample rows and builds a form and a table with proper field types. Formulas become app logic you can read and review.
You can keep the sheet as the data source while people move to the app, which adds validation, roles and a Sign-off without changing where the data lives. When the sheet becomes too slow or too important, import it into Stockroom in one step and the app switches over. Either way, each edit is recorded in the Logbook with the person who made it.
02 — What you can do
Sheets as a source
Read and write rows in place, with types and checks the sheet can't enforce.
One-step import
Move a sheet into Stockroom, Chamfer's managed Postgres, when it outgrows the file.
Edits by name
Every change made in the app is logged with the person, old value and new value.
03 — FAQ
Before you connect Google Sheets
Can people keep editing the sheet directly?
How does Chamfer access our sheets?
What happens when a sheet gets too large?
Do our column names need to be clean?
04 — Pairs well with
Teams often connect these next
05 — Used in
Dashboards on warehouse data that people can act on, with access by team, region or site written as one rule.
Route refunds, discounts, vendor changes and releases to a named approver, with the diff and the decision on record.
Turn the shared sheet everyone is afraid to touch into an app with validation, roles and a named owner.
