Everything you need to run your store with Strap.
Strap brings retail POS, inventory, products, customers, staff, branches, expenses, reports and online selling into one commerce workspace. These docs explain how to use the product, not just how the software is built.
Start quickly
Set up your shop, add products and make your first sale.
Stay organised
Keep stock, customers, expenses and orders connected.
Sell online
Publish a catalogue and manage online orders from Strap.
Quickstart
Strap is designed around the daily rhythm of a shop. After creating or opening your workspace, start with your store profile, add products, then use the POS for sales. You can enable the online storefront when you are ready.
- 1
Create your workspace
Complete onboarding and confirm your store details.
- 2
Add your catalogue
Create products with names, prices, SKUs, barcodes and stock.
- 3
Make a sale
Open Point of Sale, search or scan an item, then complete checkout.
- 4
Review the business
Use inventory, expenses, reports and insights to understand the day.
- 5
Go online
Configure the online store, publish products and start receiving orders.
Your workspace
The Strap workspace connects the operational parts of a retail business. Your store is the tenancy boundary: products, stock, sales, customers, staff activity and other records belong to the appropriate store context.
A high-level view of activity and business signals.
Catalogue, pricing, SKU, barcode and inventory management.
Fast cart building, scanning, checkout and receipts.
Public catalogue, storefront configuration and orders.
Products & inventory
Create and maintain the products you sell. Keep identifiers such as SKU and barcode consistent so search and scanning remain fast. Inventory is tracked with branch-aware stock records where applicable.
- Add products manually or import a catalogue.
- Set pricing, identifiers, categories and stock information.
- Review low-stock and out-of-stock items before they affect sales.
- Use branches and transfers when stock moves between locations.
Point of sale
Point of Sale is the counter workflow: find or scan products, build a cart, review totals and complete the transaction. Compatible camera, USB and Bluetooth scanner workflows depend on the device and browser.
Find a product → Add to cart → Review quantity → Complete payment → Issue receiptCustomers
Customers are scoped to your store. Use customer records to keep useful purchase relationships organised and make repeat service easier.
Staff & roles
Store roles help owners, managers and cashiers work with appropriate access. Give team members only the access they need for their responsibilities and review account activity when something looks unusual.
Branches
Branches represent business locations. Branch-aware inventory and transfers let a business keep stock organised as products move between locations.
Expenses & reports
Record expenses alongside sales and use reports and insights to understand performance, stock value and operational signals. Reports are decision-support tools: use them to identify what needs attention rather than simply collecting numbers.
Online storefront
Strap can publish a shareable storefront so customers can browse products and place online orders. Public storefront pages are designed to be discoverable, while private management pages remain behind authentication.
Catalogue
Choose the products that should appear online, organise categories and keep product information accurate. Public product pages should contain useful names, descriptions and imagery because this is the content customers and search engines can understand.
Orders & fulfillment
Online orders connect the customer-facing storefront with the operational workspace. Review order details, status and fulfilment information from the online-store workflow.
Store builder
Use the store builder and advanced editor to configure the presentation of your online shop. The builder is for creating the customer-facing experience; this documentation explains how to use it, not how to modify Strap's internal source code.
Account & sign in
Sign in to access private business tools. Strap uses authenticated sessions for protected areas. If your session expires, sign in again rather than trying to bypass the application access controls.
Security
Strap uses Supabase Auth and PostgreSQL Row Level Security for protected data access. Keep publishable browser keys limited to their intended use and never expose service-role or other secret keys in client-side code. RLS is the database-level boundary that protects tenant records.
Privacy & data
Use the public privacy and terms pages for legal information. Within the product, follow the account and security controls provided by Strap. Do not place secrets, passwords or private credentials into product descriptions, support requests or other public fields.
Theme & display
Strap uses light mode by default. Open Settings → Theme & display to choose Light, Dark or System. Your preference is saved to your account and restored when you sign in. Authentication and connection-approval screens stay in light mode for a consistent, readable security experience.
AI agents & MCP
STRAP MCP lets compatible AI assistants, including Claude, connect to your workspace through OAuth 2.1. The connection is tied to the signed-in STRAP user and the OAuth application, rather than a shared database password or service-role key.
https://lhizunrljottkhemdfei.supabase.co/functions/v1/mcpApprove access on first connection
The STRAP approval screen lets an owner or manager choose a store, select all branches or specific locations, and decide which information the assistant may read. Expense and customer access start disabled. Product creation, product updates and stock changes are also disabled until explicitly enabled.
Manage or revoke a connection
Open Settings → Connected applications to review authorised AI apps, edit each app's branch and action permissions, or revoke its OAuth grant. Revoking a grant invalidates that app's active OAuth tokens. Changes to a connection's access apply to its future MCP requests.
Available capabilities
- Identify the connected STRAP user and list authorised stores.
- Search products, review stock, branches, sales, expenses and customer records when permitted.
- Create products, update catalogue details and set exact stock quantities when write access is enabled.
Branch selection applies to branch-level inventory, sales, expenses and stock updates. Product catalogue edits are store-wide. STRAP does not currently expose AI write tools for payments, refunds, staff permissions or store deletion.
Source code access
The public documentation is primarily for learning how to use Strap. The application source repository is maintained separately. If you are an authorised contributor or have repository access, use the repository's normal Git workflow.
git clone <repository-url>
cd storefront-flow
npm install
npm run devDo not publish credentials or private environment values from a local setup. Browser configuration should use the publishable Supabase key; secret keys belong on trusted server-side infrastructure.
Technical architecture
Strap is built with React, TanStack Start, TypeScript, Vite and Supabase, and is deployed through Vercel. The browser uses Supabase client integration for authenticated application workflows while database access is constrained by RLS. Public store routes expose customer-facing catalogue content.
React 19, TanStack Router/Start, TypeScript and Tailwind CSS.
Supabase Auth, PostgreSQL, RLS and server-side functions where needed.
Vercel production deployments with Git-based delivery.
Canonical metadata, robots.txt, sitemap.xml and crawlable storefront pages.
Troubleshooting
I cannot access my workspace
Confirm you are signed in and that the correct store context is selected.
A product is missing
Check the current store, product status, catalogue filters and inventory records.
A scan does not work
Check camera permissions or scanner connection and test keyboard-wedge input if supported.
An online order is not visible
Refresh the online-store orders view and confirm that the order belongs to the current store.
I see an authorization error
Do not bypass access controls. Confirm your membership and role, then sign in again if the session is stale.
FAQ
What is Strap?
Strap is a commerce operations platform combining retail POS, inventory, products, customers, staff, branches, reports and online selling.
Is Strap an online store builder?
Yes. Strap includes an online storefront and store-building tools alongside the operational retail workspace.
Is Strap a POS system?
Yes. Point of Sale is one of the core workflows, alongside inventory, customers, expenses and reporting.
Is Strap like Shopify or Wix?
Strap overlaps with ecommerce and store-building products, but its positioning is broader around connected retail operations, including physical-store workflows.
Where can I learn how to use Strap?
This documentation is the main public product guide. Start with Quickstart and then choose the workflow you need.
Receipt preferences and printing
Store owners and managers can configure receipt branding and content in Settings → Receipts. Preferences include business identity, logo URL, address, phone, email, tax ID, header and footer wording, receipt prefix, paper width, copy count, text size and header alignment.
Receipt content can be tailored to show or hide the reference, timestamp, customer, branch, item details, subtotal, tax, payment method and closing message. The live preview helps check the layout before saving. POS printing uses the saved store preferences when available; browser pop-up and printer permissions still apply.
Receipt settings are store-scoped. Only owners and managers can save them. Cashiers can use the receipt workflow according to their existing role permissions.
Offline sales and synchronization
When supported connectivity is unavailable, Strap can queue eligible sales locally with a stable transaction identifier. The application retries synchronization when the device reconnects and checks for an existing transaction before replaying a queued sale to reduce duplicate-sale risk.
Keep the device secure and reconnect regularly. Confirm queued sales have synchronized before clearing browser storage, signing out of a shared device or moving to another device. Offline mode does not guarantee conflict-free stock reconciliation across multiple devices.
Connected apps and access
Connected applications and MCP clients use explicit per-client authorization grants. Store owners can review available access, approve the permissions requested for an integration and revoke grants that are no longer needed. Audit events support security review and accountability.
Never share staff PINs, account passwords or private API credentials with an integration. Give external clients only the access needed for their task.