The starting point
Shopify handles core commerce and straightforward inventory well. Complexity starts to show up with components, raw materials, multi-level BOMs, supplier workflows, landed cost, and deeper planning needs.
OPERATIONAL COMMERCE OSERP-level operational control, built for Shopify.
Manage purchasing, receiving, scanning, cost visibility, and replenishment through modular tools that share one operational backbone. Start with the workflow you need now, then add depth as your volume grows.
Built for the operational gap Shopify merchants hit next.
You're here if:
- You manage multiple Shopify locations, warehouses, or inventory workflows.
- Your inventory includes bundles, kits, components, or raw materials Shopify was not built to model.
- Your team spends real time on purchase orders, receiving, and landed-cost reconciliation.
- You've hit the ceiling of Shopify's native reporting, valuation, or planning tools.
- Full ERP quotes feel too expensive, too slow, or too disruptive for where you are today.
Why modular operations, not a full ERP rollout
Shopify is strong at commerce. ERPs are built for broad enterprise control. The hard part is the operational layer in between: purchasing, receiving, inventory accuracy, landed cost, and replenishment.
Zapstra gives merchants that depth through modular tools that can run independently or together on one shared operational backbone.
THE LANDSCAPENATIVE SHOPIFY 
FULL ERP
ZAPSTRA OPERATIONAL COMMERCE OS
Three paths, one decision.
The heavy lift
Enterprise systems offer broad operational control, but rollouts come with significant cost, process change, and adoption risk that can outpace the value delivered.
The modular path
Start with the workflow that hurts most — purchasing, receiving, scanning, costing, or replenishment. Add modules as volume grows, while every module stays connected through the same operational backbone.
Gartner predicts that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals. Gartner ERP research ↗
THE SUITE
Four modules. One shared backbone.
AVAILABLE
SupplierOps
Procurement control built for Shopify: supplier directory, purchase orders, receiving, materials management, and migration off Stocky.
BetaIN DEVELOPMENT
StockScan
Native iOS and Android scanner companion for receiving, counts, lookups, and variance capture. Designed for the warehouse floor.
In DevelopmentClearCost
Inventory cost truth with component-level visibility: material, freight, duty, and overhead — broken down per unit, explainable per receipt.
In DevelopmentRestock
Reorder signals you can trust: lead-time-aware, MOQ-aware, BOM-aware. Recommendations grounded in real history, not spreadsheet theater.
In DevelopmentPLANNED
More on the way
CONNECTED BY DESIGN
One backbone. Every workflow.
Zapstra is built around a shared operational record for suppliers, purchasing, receiving, inventory movement, cost visibility, and history. Each module can stand on its own, but the data stays connected when your system grows.
That means you can start where the pressure is highest, add the next workflow when volume justifies it, and avoid rebuilding your operations across disconnected apps.
MIGRATION WINDOW
Request migration beta access → Shopify Stocky retires August 31, 2026.
SupplierOps migration tooling is live in beta — bring your suppliers, purchase orders, and receiving history into a system built to grow with you.
Common questions
- Do I have to install the whole suite?
- No. Each module is designed to run independently. Start with the workflow under the most pressure, then add modules when the work and volume justify it. For many teams, SupplierOps is the natural first step because purchasing and receiving are where Shopify's native tooling reaches its limits first.
- What happens to my data when modules connect?
- Zapstra modules work from the same operational backbone. Suppliers, inventory history, purchase orders, cost data, and activity carry forward as you add modules — so you are not rebuilding context or reconciling data across separate apps.
- Is this a replacement for my ERP?
- Zapstra can replace many of the operational workflows teams often look to an ERP for: procurement, receiving, costing, scanning, and replenishment planning. It does not replace accounting, payroll, HR, or corporate finance systems. Most merchants use Zapstra as the Shopify-centered operations layer alongside those tools.
- How does this compare to Stocky?
- SupplierOps is built for the supplier, purchase order, and receiving workflows Shopify merchants used Stocky for, with added attention to migration, auditability, cost-layer visibility, and connected inventory operations. Stocky migration tooling is currently in beta.
- Are you Built for Shopify certified?
- Status is handled module by module. BundlesIQ is listed in the Shopify App Store; OS modules are moving toward public listing and review. We do not present unreleased modules as certified — ask us for the current status of any specific module.
- Can I use this with my existing apps?
- In most cases, yes. Zapstra is designed to sit alongside your Shopify stack. The OS modules share a backbone with each other, while existing apps can continue handling the workflows they already own. During onboarding, we'll flag any overlap around inventory, fulfillment, purchase orders, or cost data before it creates conflicts.
- How is pricing structured?
- Pricing is based on the work your operation needs to handle — not artificial seat walls, hidden feature gates, or enterprise-only access. Start with the module that fits your current workflow, then scale as volume and complexity grow.
- What's your roadmap?
- Modules ship individually, not as one large release. The Suite section above shows each module's status across Available, In Development, and Planned, so you can see what is usable now and what is coming next.
- How do I get started?
- Request beta access for the module you need most. We review each request — beta seats are intentionally limited so early users get the attention and stability they need. If we're not the right fit yet, we'll tell you when we are.
Ready to see if it fits?
Request beta access for the workflow under the most pressure today. We're being intentionally selective so early users get real attention as the modules mature.