# Ecommerce development

> We build commerce systems and the operational stack they depend on: the storefront, the catalogue, and the integration to the ERP, the CRM and the warehouse that have to agree with it. Most of this work is B2B, where the order is the start of a process rather than the end of one.

For: Operations and product leaders whose orders cross more than one system
Canonical: https://www.techfabric.com/software/ecommerce

---

Ecommerce that agrees with the ERP behind it

A storefront is the easy half. The order it creates has to reach an ERP, a warehouse and a finance system that were not designed together, and that is where commerce projects actually go wrong.

## What you get

- The storefront and the catalogue, with the pricing and entitlement rules B2B buyers actually have
- The integration between commerce, CRM and ERP, which is where AmTab's project mostly lived
- Order flow through to the warehouse, on Dynamics 365 with Insight Works as we did for Funko
- Business Central or Dynamics 365 as the system of record, configured rather than forked
- The reporting layer, because the question after launch is always which lines are moving
- Headless where it earns it. Medusa, Saleor and commercetools are worth the extra moving parts when the catalogue or the pricing rules outgrow a hosted platform, and not before

## Questions

### Do you build the storefront or the ERP?

Both, and the integration, which is usually the part that decides whether the project works. For AmTab we built the Business Central ERP, amtab.com, and the connection between ecommerce, CRM and ERP. We have also built a commerce engine and an ERP end to end for a California wine retailer.

### Shopify, or something custom?

Shopify where the catalogue and the pricing fit it, because you should not pay us to rebuild what it already does well. B2B is where it starts to strain: customer-specific pricing, entitlements, quote-to-order and approval chains. We will tell you which side of that line you are on before you commit to either.

### Is headless commerce worth it?

Sometimes, and it is oversold. It buys you a catalogue and a checkout you can shape without fighting a template, and it costs you a front end, a deployment path and a team that has to own both. Worth it when the pricing or catalogue rules are the product. Not worth it for a catalogue a hosted platform would have served.

### We already have an ERP. Can you work with it?

Usually, and it is the common case. The first question is what the ERP is willing to tell you and how quickly, because a storefront that reads stock every thirty seconds and one that reads it nightly are different systems. We would rather find that out in week one than in the week you go live.