01
Retail checkout
Handle the in-person sale with the same catalog used by the broader business.
Build
Path feature guide
Connect checkout to the rest of the operation.
Build an on-site sales experience that shares customers, products, inventory, and reporting.
Product screenExample data
checkout.path.dev
Point of saleOperations
Orders
Search…
New
| Order | Customer | Status | Total |
|---|---|---|---|
| #18412 | Nora Velez | paid | $184.20 |
| #18411 | Sam Ortiz | shipped | $2,140.00 |
| #18410 | Priya Shah | pending | $48.00 |
| #18409 | Jonah Reed | paid | $1,290.00 |
| #18408 | Tess Bloom | paid | $67.50 |
What this makes possible
Start with the work, then shape the system.
02
Member and guest sales
Connect purchases to the people, memberships, stays, or properties behind them.
03
Operational reporting
Keep sales, inventory, and business reporting on one connected data foundation.
How to approach it
A practical starting path.
The exact implementation depends on your data, permissions, operating model, and connected systems.
- 01
Map the transaction
Define products, modifiers, taxes, tenders, receipts, and the record of sale.
- 02
Connect operations
Align inventory, customer identity, fulfillment, and downstream reporting.
- 03
Test the counter
Verify hardware, permissions, payment states, reversals, and end-of-day workflows.
Customer proof
See it in a real business.
Customer stories are shown only where the published story names a related Path capability.
Keep exploring
Related systems and capabilities.
Build your version.
Start with one useful workflow, then connect the rest as the system proves itself.