Not building a separate wholesale mode

Alternatives considered

Discarded

Build an independent wholesale mode.

Chosen

Build unit, box, and bundle presentations, along with stock reservations, into the core.

Decision made

Treat retail and wholesale as profiles of the same domain and include presentations and stock reservations in the product core from the start.

Rationale

Those capabilities apply to both profiles; building them once avoids duplicating logic later.

Frequently asked questions

What did Pymerce decide about "not building a separate wholesale mode"?

Treat retail and wholesale as profiles of the same domain and include presentations and stock reservations in the product core from the start.

Is it better to run wholesale and retail on the same system, or keep them separate?

At Pymerce, treating them as profiles of the same domain avoids building and maintaining two parallel systems. The shared logic — unit, box, and bundle presentations, stock reservations — gets solved once for both profiles.

What would have ended up duplicated if Pymerce had built a separate wholesale mode?

Product presentations (unit, box, bundle) and stock reservations would have had to be built twice — once per mode — with the risk of the two versions drifting out of sync over time.

What capabilities do retail and wholesale share in Pymerce?

Unit, box, and bundle presentations, along with stock reservations, are built into the product's core because both profiles need them — not bolted on as an extension from one mode to the other.