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 equivalent, not a public retail storefront platform.
Every capability below runs in production today.
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 runs today, and what Commerce does not include.
Procurement, inventory by location, truck stock, and AP vendor bills run in production on the same vendor and product records as Service and Finance.
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, and 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.
Commerce does not include
Commerce is built for trade contractors who sell product alongside service work. It does not include the following. Sales tax stays with your tax provider or accountant.
- A public retail storefront with themes
- A pick, pack, and ship fulfillment pipeline
- Returns and RMA workflows
- A sales tax engine
- 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, all running today.
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, 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.
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.
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 equivalent — 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.
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 by configured rules. 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 by configured rules. Available today.
4. One customer, every channel.
The customer who booked the install last March is the customer who buys the follow-up 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, and reconciliation. Available today.
6. A product catalog built for the job.
Your team looks up parts, pricing, and availability on the job, and the same product lands on the invoice. Available today.
7. Orders ride the work order.
Product orders run inside the Service work-order flow, so the part, the visit, and the invoice stay on one record. Available today.
The operating principles behind Commerce.
These are the rules we hold ourselves to. They are why this page lists only what runs today.
Clear scope, stated plainly.
Every capability on this page runs in production today. What Commerce does not do is listed plainly, so you can plan around it instead of discovering it after you buy.
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.
Available means proven.
A capability appears on this page after a real tenant has used it in production on a real order.
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?
- No. Commerce is not a public retail storefront. The product catalog, customer accounts, and Stripe payments are live for service-attached product sales. If you need a public retail storefront, 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 part of Commerce. 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.
- 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 exchange?
- Commerce does not include a returns or RMA workflow. Keep handling returns, vendor returns, and warranty exchanges in your current process.
- 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 by configured rules.
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. Catalog, customers, procurement, inventory, AP, and Stripe payments are live.
Already on Guspora for service work? See how Service feeds Commerce.