Buy parts. Stock trucks. Bill the job. Sell the spare. One record.
The faucet bought on a vendor PO, received into the warehouse, transferred to a truck, billed on a service ticket, and sold to the customer as a part are the same row. Commerce is the trade-contractor commerce surface for Guspora — procurement, multi-location inventory, AP, and service-attached product sales on Stripe. Not a Shopify replacement, not a public retail storefront platform.
Honest scope below. Some pieces are live. Some are in progress. Some are not built. We mark every one.
Trade contractors who sell parts, equipment, and accessories alongside the work.
Plumbing, HVAC, electrical, fire protection, low-voltage, irrigation, locksmith. Anyone whose techs install something that has a part number, a vendor, and a markup. Anyone who today copies the same SKU between an invoicing system and a separate online store and watches the two go out of sync.
A good fit
- Service contractors who also sell product to existing customers
- Shops where the same SKU shows up on a work order and on a counter sale
- Businesses already using Guspora for service work that want product sales on the same record
- Operators who would rather start narrow and grow than buy a 50-app marketplace
Not a fit
- Pure-play retailers whose entire business is the storefront
- Operators who need a public retail storefront with marketing automation in production this quarter
- Wholesale-first businesses that need B2B EDI to distributors
- International sellers needing multi-currency storefronts
If you are a pure-play retailer, this is not your tool. Run Shopify or BigCommerce. They are very good at being a storefront.
What is built today, what is in progress, and what is not in the near-term roadmap.
An audit on May 11, 2026 closed the procurement, inventory-by-location, truck-stock, and AP-vendor-bill claims — those run in production today on the same vendor and product records as Service and Finance. The customer-facing storefront templates and end-to-end cart are still in progress, and the dedicated order pipeline and RMA are not built. We will not market what is not finished.
Available today
Price book, customers, payment, procurement, AP.
Tenant price book
Per-tenant catalog with vendor mapping, categories, search, and Stripe price sync. One product record across Service, Commerce, and Finance — the same SKU billed on an inspection is the SKU sold as a part.
Customer accounts
Service customers are commerce customers. One account, one history, one balance. Live and in production from the Service module.
Stripe payment infrastructure
Live payment intents, refunds, Stripe Connect, webhook reconciliation. The same payment plumbing that handles service invoicing and subscription billing today.
Procurement, POs, and inventory by location
Buy from your vendors on POs, receive against the PO into warehouse, shop, or truck stock, transfer between locations, and decrement on work orders. Reorder suggestions and low-stock alerts ship today.
AP vendor bills
Vendor invoices captured against the PO with three-way match, approval pipeline, and downstream payment. The bill that pays the vendor for the part is the same record as the receipt and the PO.
In progress
Storefront and checkout, piece by piece.
Storefront templates
Tenant-branded product pages and customer-facing browsing. In design. Today the catalog is internal — used by your team on jobs and on invoices, not a public retail destination.
Full cart and checkout
The Stripe primitives are live. The end-to-end cart, address-capture, and order-confirmation flow is being assembled and has not been proven through a full production checkout cycle.
Cycle-count and reconciliation tooling
Stock locations and reorder rules are live. The full physical-count workflow (handheld count, variance reconcile, audit trail) is shipping piece by piece on top of the inventory ledger.
Not built today
We will not pretend otherwise.
Order pipeline (pick, pack, ship)
Dedicated commerce order pipeline with barcode picking, partial shipments, and backorder handling. Not built. On the roadmap, designed in detail and gated on operator approval to begin.
Shipping orchestration via ShipStation
Buy labels, compare carrier rates, push tracking back to channels. Designed as a downstream adapter that runs after the order pipeline lands -- ShipStation is the shipping edge, not the source of truth. Not built today.
Marketplace channel connectors (eBay, Walmart, Amazon)
List, sync inventory and price, import orders, publish tracking back to the channel. Designed under one shared adapter contract so a Guspora product is one record across every channel. Not built today; lands after the order pipeline and ShipStation.
Returns and RMA
Restocking rules, vendor returns, warranty replacement routing. Not built. On the roadmap behind the order pipeline.
Built-in tax engine
Sales tax is your responsibility today. We do not ship a tax engine. Use your existing tax provider or accountant. We will not pretend otherwise.
Not in the near-term roadmap
Commerce starts narrow. These are not in the near-term build queue. We will revisit them as the platform and our customers’ needs grow into them — but we are saying so up front so you do not buy this expecting them today.
- Multi-currency international storefronts
- Dropship marketplace fulfillment
- B2B EDI integrations with distributors
- A migration path from or import path out of Shopify
- A 50-app extension marketplace
- Abandoned-cart marketing automation
The pieces, with honest labels.
The small wins are the real ones. The same product is the line item on the inspection invoice, the line item in a sale, the receipt against a PO, and the line on the vendor bill. One customer record across both. That is what makes this worth running on Guspora instead of bolting on a second platform.
Tenant Price Book
Available nowPer-tenant catalog of parts, equipment, and services with vendor mapping, categories, search, and Stripe price sync. The faucet you bill on a service ticket and the faucet you sell as a part are the same row across Service, Commerce, and Finance.
Shared Customer Accounts
Available nowA customer who books a service call and a customer who buys a part are the same account. No parallel email list, no second login, no second history. Already in production for Service.
Stripe Payment Infrastructure
Available nowStripe Connect, payment intents, refunds, webhook reconciliation, and payment-method storage. The same engine that processes service invoices and subscription billing today.
Procurement & Purchase Orders
Available nowBuy parts from your vendors on POs that flow into receiving, inventory, and AP bills. Draft → submit → approve → order → partial / full receive, with vendor mapping and per-PO line items. Live in production from /company/procurement.
Multi-Location Inventory
Available nowWarehouse, shop, and truck as first-class stock locations. Receive against POs, transfer between locations, deduct on work orders, and run reorder suggestions. Live. Cycle-count tooling is shipping piece by piece.
Truck Stock & Restock
Available nowPer-technician truck inventory, low-stock alerts, and replenishment requests that route back to procurement. The part the tech used on the van is decremented from the truck, not the warehouse.
AP Vendor Bills
Available nowVendor invoices captured against the PO, three-way match between PO / receipt / bill, approvals, status pipeline (draft → submitted → under review → approved → rejected → paid), and downstream payment. Live.
Storefront Templates
In progressTenant-branded category pages, product detail, search, and customer self-serve. Today the catalog is internal — referenced by your team on jobs and on invoices. Public-storefront templates are in design.
Cart & Checkout
In progressCart persistence, address capture, and checkout flow. Stripe payment under the hood is live; the front-of-house checkout experience is being assembled and is not yet end-to-end proven.
Order Pipeline
RoadmapDedicated pick / pack / ship pipeline with barcode picking, partial shipments, and backorder handling. Not built. Orders today ride inside the Service work-order flow that already exists.
Returns & RMA
RoadmapReason codes, restocking rules, vendor return routing, warranty replacement that knows where the part went. Not built today. On the roadmap behind the order pipeline.
Where Commerce stands today, next to Shopify.
Shopify is for retailers. It is excellent at being a public storefront with theming, marketing automation, abandoned-cart flows, app extensions, and a checkout that has been hardened over millions of orders. If your business is selling product to the public on the internet today, Shopify or BigCommerce is the right answer for that job. Today, Commerce is not a Shopify replacement — it is the service-attached product channel for trade contractors.
Commerce is for contractors who happen to sell product. The job is different. Your customer is already in the system because they had a service call last year. Your product is already in the system because your tech billed it on a work order last week. The job is not building a storefront from a blank slate — the job is letting that customer buy that product without your team copying the SKU between two platforms.
If you need a public storefront with marketing, abandoned-cart flows, and a 50-app ecosystem today, Shopify is the proven answer. If you need product sales attached to the same record as your service work, customers, and finance, that is us -- and the public-storefront depth is on the roadmap.
We will not say "cancel Shopify." Plenty of contractors will run both, and that is fine. Shopify out front for the retail channel, Commerce inside for the service-attached product sales. They will not talk to each other automatically. We are not pretending they will.
The part you bought yesterday is on the truck today and on the invoice tomorrow.
1. One price book, every channel.
SKUs, variants, kits, vendor mapping, and warranty terms live in one product record. The product on a Service work order is the same record consumed by a Commerce sale and the same row a PO buys against. Available today.
2. Procurement on the same record.
Draft a PO against a vendor, submit for approval, order, partial / full receive into warehouse / shop / truck stock. The AP bill that pays the vendor is three-way matched to the PO and the receipt. Available today.
3. Truck stock and reorder live.
Each technician carries first-class truck inventory. The part used on a work order decrements the truck, not the warehouse. Low-stock alerts and reorder suggestions route back into procurement automatically. Available today; the deeper physical-count workflow is shipping piece by piece.
4. One customer, every channel.
The customer who booked the install last March is the customer who buys the replacement filter today. Same account. Same history. Same balance. Available today.
5. Stripe payment under everything.
The same Stripe Connect plumbing that handles your service invoices handles a Commerce sale. Refunds, payment-method storage, webhook reconciliation. Available today.
6. Internal product catalog before public storefront.
Your team can look up parts, pricing, and availability on a job today. The public-facing storefront templates are in design. Treat the customer-browsing experience as preview, not production.
7. Order pipeline and RMA come later, on purpose.
We did not ship a half-finished pick-pack-ship system. We will ship it when it is real. Until then, orders ride inside the Service work-order flow that already exists.
The operating principles behind Commerce.
These are the rules we hold ourselves to as this module matures. They are the reason the page above marks things as in progress instead of glossing over them.
Honest scope before clever marketing.
A May 2026 internal audit flagged Commerce as partial. We could have written marketing copy that hid that. We did not. Every section on this page tells you what is live, what is in progress, and what is not built — and we hold ourselves to that line in the product, not just on the website.
One record, not a parallel database.
A Commerce customer is a Service customer is a Finance customer. A Commerce product is a Service line item is a Finance cost-of-goods row. We refused to build a second product table, a second customer table, or a second payment integration. The whole point is that there is only one of each.
No half-finished pretending.
We did not ship a pick-pack-ship workflow that almost works. We did not ship an RMA flow with three of the seven cases handled. When we mark something available, it has been used in production by a real tenant on a real order. Until then it carries an in-progress or roadmap badge, plainly.
Sales tax is your responsibility.
We do not ship a tax engine. We will not calculate, file, or remit on your behalf. Use Avalara, TaxJar, your accountant, or whatever your existing setup already handles. We will not pretend the tax problem is solved when it is not — that is the kind of half-truth that gets contractors audited.
Where Shopify wins. Where we are useful.
Today, we are not pretending to beat Shopify at being a storefront. We are going to be honest about the trades.
The honest read: if your business is the storefront, Shopify is the right answer. If your business is service work and product sales are an attached channel, Commerce is the right answer — for the pieces that are live today, with the rest arriving piece by piece.
The questions every contractor asks before buying a commerce tool.
- Can I run a public retail storefront on this today?
- Not in the way Shopify means it. The product catalog and customer accounts are live, and Stripe payment is live, but the public storefront templates and full end-to-end checkout are still in progress. Today, treat Commerce as your internal product catalog you reference on service jobs, with checkout coming online piece by piece. If you need a public retail storefront in production this quarter, run it on Shopify and let Commerce handle the service-attached product sales.
- Can I sell wholesale or to other contractors?
- Per-customer pricing rides on the same customer record we already use for Service, so the data model supports it. The dedicated wholesale workflow -- net-terms gating, restricted catalogs, B2B EDI to distributors -- is not in the near-term build queue. If wholesale is your primary channel today, run that on a wholesale-first tool and use Commerce for the service-attached product sales.
- What about sales tax?
- We do not ship a tax engine. We do not calculate, file, or remit sales tax on your behalf. Use your existing tax provider, your accountant, or a dedicated tax service like Avalara or TaxJar through your own integration. We will not pretend the math is solved when it is not.
- Inventory across multiple trucks?
- Available today. Warehouse, shop, and per-technician truck stock are first-class records. The part used on a work order decrements the truck the tech is driving, not the warehouse. POs receive against the correct location; transfers move stock between locations; low-stock alerts and reorder suggestions feed back into procurement. The full physical-count / variance-reconcile workflow is shipping piece by piece on top of the inventory ledger — treat that one as the maturing edge, not the whole system.
- Do you handle purchase orders and AP vendor bills?
- Yes. Procurement is live at /company/procurement — draft a PO against a vendor on the price book, submit for approval, order, receive against the PO (partial or full) into warehouse, shop, or truck stock. The AP vendor bill captured against the PO is three-way matched to the receipt and routes through the same approval pipeline before payment. One record from the PO line to the receipt to the bill to the payment.
- Returns, RMA, and warranty replacement?
- Not built. The returns flow, vendor-return routing, restocking rules, and warranty-replacement logic that knows whether a part is on a customer truck or in scrap — none of that ships today. It is on the roadmap, behind the order pipeline. If you need RMA tooling now, do not buy this expecting it.
- Does this integrate with my existing Shopify store?
- No. There is no Shopify import, no two-way sync, and no migration path. Commerce is a separate channel that lives where your service work and your customer record already live. If you want to run Shopify out front for retail and Commerce inside for service-attached product sales, that is a reasonable setup — they will not talk to each other automatically.
Ready to sell product on the same record as the rest of the business?
Commerce is part of every Guspora tenant once enabled. No separate login, no separate billing, no separate customer database. Honest scope: catalog, customers, and Stripe payment are live. The rest is in progress, and we will tell you exactly where we are when you ask.
Already on Guspora for service work? See how Service feeds Commerce.