Inventory and replenishment
Stock by store and SKU with safety-stock alerts, transfer drafts and purchase order requests.
Retail
Store and supply tools built by AI, on the systems your stores already run
Stock counts, markdown approvals, order exceptions and store audits still live in spreadsheets and WhatsApp groups. Describe the tool and ToolJet builds it on your POS, e-commerce and ERP data, scoped so each store manager sees their store and head office sees the chain.
- Inventory and replenishment views
- Store operations checklists
- Order exception queues
Store operationsRegion North · todaySSOAudit onProduction
Stores reporting46 / 482 pending close
Low-stock SKUs12718 below safety stock
Markdowns awaiting approval9$14,300 total
| Store | Manager | Task | Status |
|---|---|---|---|
| Manchester Arndale | P. Raman | Weekly stock count | Complete |
| Leeds Trinity | D. Okafor | Markdown request · 14 lines | In review |
| Liverpool One | M. Lin | Planogram audit | Overdue |
| Sheffield Meadowhall | T. Herrera | Weekly stock count | Complete |
When a SKU falls below safety stock in any store, draft a transfer from the nearest store with surplus
Stock trigger and transfer draft query added · awaiting your review
41,000+stars on the open-source core
SOC 2 Type IIISO 27001 and GDPR · Visit the trust centre
Your infrastructureCloud, VPC, on-premise or air-gapped
100+ connectorsplus any REST or gRPC endpoint
No engineering ticket needed
Describe the tool you need. ToolJet builds it.
Type what you want in plain language. ToolJet generates the pages, queries and logic as a working app. Connect your data, set who can see what, and review the generated logic before publishing. Edit the app on the canvas afterwards.
- Working app, not a mockup
- Review access rules before publishing
- Free to start, per-builder pricing
Built on the systems retail teams already run
WooCommerce
Stripe
SAP HANA
PostgreSQL
MySQL
Google Sheets
Zendesk
Slack
Have developers? They can build the same apps from
through the ToolJet plugin
What retail teams build with ToolJet
Store operations checklists
Opening, closing, audits and counts, scoped per store, with completion visible by region.
Markdown and price-change approvals
Requests with margin impact, threshold-based routing and a decision record.
Order exception handling
Failed payments, address problems and split shipments in one queue with guarded actions on your order system.
Supplier and delivery tracking
Fill rates, late deliveries and returns per supplier, from your ERP and carrier data.
Customer service consoles
Order lookup across e-commerce, payments and tickets so agents stop switching tabs.
How retailers roll it out
- 01
Connect the commerce stack
POS, e-commerce, payments and ERP connect once with scoped credentials. Builders use them without seeing secrets.
- 02
Scope by store and region
Configure store and regional roles, enforce external record restrictions in server-side queries, database policies or APIs, and test each role before rollout.
- 03
Start with one process
Stock counts or markdowns first. Pilot in a region, refine on the canvas, then roll out to the chain.
- 04
Automate the follow-through
On Self-hosted, scheduled and event-driven workflows raise transfers, notify managers and post updates to Slack or Teams.
In production
Teams already running on ToolJet
Built in, not bolted on
The controls your compliance team already expects
Configure store and regional access so staff work with the records they are authorized to use. Team includes SSO and platform audit logs; record stock adjustments and approvals explicitly in your systems.
Single sign-on and SCIM
SAML, OIDC and LDAP on Team and above. Enterprise adds SCIM provisioning and directory group sync.
App and data permissions
Configure app and resource access in ToolJet. Enforce external record restrictions in server-side queries, database policies or APIs; hiding a component does not authorize access.
Platform audit logs
Team includes platform audit logs. Confirm event coverage, retention and export for your deployment; store business decisions and rationale explicitly in your apps.
Runs where you say
Choose managed ToolJet Cloud or self-host in your VPC or on-premise. Builder BYOK is available on Enterprise plans for both Cloud and Self-hosted. Air-gapped operation and a customer-hosted AI gateway require separate Self-hosted Enterprise add-ons. Local inference also requires a supported local model.
Security and governance features vary by plan. Workflows and Agent Builder are available on Self-hosted only; BYOK is available on Enterprise plans for both Cloud and Self-hosted. Compare plan availability.
Two ways to get there
Build it yourself, or bring our engineers in
Self-serve
Your team, your pace
Start free. Describe the tool, refine it on the canvas, and ship it under your own access rules. Start with one app, then test it with your team before rolling it out.
Start free
Professional services
Forward-deployed engineers, embedded with your team
When the timeline is fixed or the process is tangled, our engineers build alongside you: scoped delivery, production-ready apps, and knowledge transfer so your team owns the result.
Talk about a projectFrequently asked questions
Can each store manager see only their store?
Yes, with configured access controls. Enforce store and region restrictions in server-side queries, database policies or APIs, and test read and write actions for store managers and head-office roles.
Does it work with our POS and e-commerce platform?
ToolJet connects to WooCommerce, Stripe, SAP and your databases natively, and to any POS or commerce platform with a REST, GraphQL or gRPC API, alongside 100+ connectors.
Can store staff use it on a phone or tablet?
Yes. Apps are responsive and can be laid out for mobile. Checklists and counts work on the shop floor.
How fast can we get a first tool live?
Start by generating an app for one process, such as stock counts or markdown approvals. Pilot in one region and validate data connections, permissions and write actions before rollout. Timing depends on integration and review requirements.
Do we pay per store user?
Pricing is per builder, not per user. Every plan includes an end-user allowance and Enterprise includes unlimited end users, so rolling a tool out widely does not add a seat for every viewer. The pricing page lists the allowance on each plan.
Give every store the same tool, and every manager their own view
See it on your commerce data with an engineer.
Page updated