One storefront or several
Catalogue, search, cart and checkout, built to stay fast as the catalogue grows. Run one store, or several brands and regions on one backend that share inventory and still look like separate businesses.
Full service ecommerce, built in Montréal.
Everything your store needs to run.Built once, run for years.
Storefront, checkout, payments, trade accounts, merchandising, finance and the operations behind them. One senior team builds it, hosts it, and keeps developing it while you run the business.
- One storefront or several
- Merchandising you control
- Promotions and pricing
- Wholesale and trade accounts
- Payments
- Shipping and fulfilment
- Operations, buy to return
- Custom built for you
- Hosted and patched
- Finance and accounting
What we build
One platform, the whole operation
Most of what makes commerce hard is not the storefront. It is everything the storefront depends on. Three parts, and you can take them one at a time.
01Sell
The shopfront and everything a customer touches.
Merchandising you control
Homepage sections, carousels and campaigns editable by your marketing team in the back office. No ticket, no deploy, no waiting for us.
Promotions and pricing
Sales, promo codes and price lists, scheduled to start and end on their own. Your team sets them up in the back office without waiting for a developer.
02Serve
Who buys, how they pay, and how it reaches them.
Wholesale and trade accounts
Sell to businesses and to the public from the same store. Trade customers apply for an account and you approve it. Once they sign in they see their own catalogue and their own prices, and each person on the account gets only the access you give them.
Payments
Keep the payment processor you already use. If it has an API, we connect it. If it needs an integration that does not exist yet, we build it. Canadian processors included.
Shipping and fulfilment
Every order gets the right box, live rates from each carrier you use, and the best carrier and service picked for it automatically. Labels print in batches and tracking goes to the customer.
03Run
The machinery behind the counter, and who keeps it running.
Operations, buy to return
Ordering from suppliers, receiving, inventory, picking, shipping and returns, with the daily jobs that run themselves. The full lifecycle a logistics operation runs on.
Custom built for you
When no platform does what your business needs, we write it: your pricing rules, your approval workflows, connections to your ERP, suppliers and warehouse, and internal tools for your team. Custom code you own.
Hosted and patched
We run the infrastructure. Security updates, monitoring and upgrades are ours, not a line on your team's backlog.
It is modular. Take the parts you need and leave the rest, and if a capability is missing, it gets built. That is the difference between a platform you rent and one that is yours.
Finance and accounting
Month end stops being a week
Closing the books should be a click, not a fortnight of spreadsheets. Most of that fortnight is not accounting. It is getting two systems to agree about what happened.
- Everything lands in your ledger
- Orders, refunds, shipping charges, taxes and payouts post to the accounting system you already run, in the form it expects, as they happen. Nobody exports a file on the last Friday of the month.
- Reconciliation runs continuously
- Processor against orders, orders against inventory, inventory against purchasing. Matched as it goes, so what reaches your finance team is a short exception list rather than a search.
- One set of numbers
- The store, the back office and the ledger read from the same source. When they disagree it is a real problem, not a formatting difference, and you find out the same day.
- Month end is a review
- Your controller checks the exceptions and closes. No re-keying, no reconstruction, and no waiting on a developer for an export that only one person knows how to run.
This is the part nobody puts on a commerce website, and it is the part that decides whether the business trusts the system.
What that looks like in practice
Case studies
NAPA Auto Parts
Four storefronts, one backend
Four separate storefronts on one commerce backend, integrated with the accounting, inventory, shipping and payment systems already in use. Trade customers get accounts governed by role, approved before they can order, where the catalogue and the pricing change depending on who is logged in.
- The marketing team runs the homepage, its sections and its carousels without a developer
- Payments run through a gateway that had no integration until we wrote one
- Catalogue, orders and customers carried across by tooling written for the job
- Delivered storefront by storefront, so the business kept selling throughout
Leaving Magento
Why staying gets riskier every month
Every Magento version has an end-of-support date. After it, security patches stop while the store keeps taking card payments. Extended support comes only with an Adobe Commerce licence. Open Source gets none.
- 2.4.6 lost regular support on 11 August 2026, and 2.4.7 follows on 31 May 2027
- Once patches stop, every newly found vulnerability stays open on the system that handles card details
- PCI DSS expects critical security patches within a month of release. An unsupported version has none to apply
- Staying means a major upgrade every few years, retesting every extension each time
A B2B operations platform
Replacing a commercial product
A distributor running on a packaged inventory and order system that no longer fit, and could not be extended. We replaced it: supplier ordering, receiving, inventory, order workflow and the scheduled jobs that keep it moving, all built around how the business actually works.
- Every person sees and does only what their role allows, and those rules are tested before each release
- A fresh copy of the system comes up in minutes, so changes are tried safely before they go live
- Purchasing, stock and orders keep moving on schedule, without anyone pressing a button
- It replaced a licensed product, so there is no licence left to renew. The system is theirs
Drag, or use the arrows.
Every one started the same way: read the existing system completely, write down what it really does, then decide what to build. A rebuild that skips that step is a guess with a budget attached.
Coming from an older platform
Moving off what you have
We assist with the migration rather than hand you a checklist. Catalogue, orders, customers and integrations come across, carried by tooling written for the job rather than re-keyed. We rebuild only what cannot carry forward, and we do it in phases so the shop never closes.
The first step
A free platform assessment
The same first step as every build above.
- from kickoff to the workshop
- ~1 week
- no cost and no commitment
- $0
- deliverables: plan, risks, what moves
- 3
Day 1
Kickoff
A call with whoever knows the system best, and you decide what is in scope.
Days 2 to 4
The diagnosis
We examine every integration, the data volumes, custom code that will not port cleanly, and the business rules nobody wrote down.
Day 5
The prescription
A workshop with your team: a phased plan, a risk register, and what moves as it is versus what has to be rebuilt.
After
Your call
If you want us to build it, we price the build from the scope we just mapped.
Get a free platform assessment
Like a good doctor, we diagnose before we prescribe.
Common questions
Before you get in touch
Talk to an engineer
Not a salesperson, and not a form that routes to one. Tell us what you are running and what is breaking.
We reply within one business day. Or email hello@productshop.io.