CommerceFlo

CommerceFlo was FactoryJet's commerce and ERP platform: online store, marketplace sync, B2B ordering, retail POS, distributor management, accounting, all sold as one system. I did not design the platform. I designed the site that had to sell it, which is a different job with a different hard part.

The hard part is the catalogue. A buyer arriving at a platform this wide does not know what to call the thing they need. The founder of a shoe label looks for Fashion. Someone doing the same job with a different vocabulary looks for D2C. A distributor looks for Wholesale and the procurement lead at that same distributor looks for B2B. Miss their word and you lose them, so the navigation carries four parallel cuts of one product: Platform, By Business Model, By Industry, By Use Case, with Automation, Integrations, Services and Resources beside them.

Every entry in every cut needs a page of its own, and every menu row carries a name plus roughly five capabilities under it. That is twenty eight destinations, in twelve weeks, with three of us, handed to a client who would be editing all of it in WordPress after we left.

• Four parallel taxonomies
• 28 destinations
• Client edits it in WordPress
• Twelve weeks, three people
• Copy written alongside design

Twenty eight bespoke pages was never going to happen in twelve weeks with three people, and twenty eight pages of the same three sections would have read as filler. What the catalogue actually needs is one skeleton with enough slots that each audience sees their own language in it, and enough discipline that a reader who lands on two of them does not feel duplicated.

So the page is a fixed sequence: hero with the audience's own promise in it, the client strip, a single blue statement band, a capability grid built from real interface, proof from that sector, then the closing band and the footer. Every slot has a defined job, which is what makes it safe to hand to someone else to fill.

The homepage is the same idea one level up. It is thirteen section components stacked, not a drawn page, so a section could be reordered or dropped without redrawing anything around it.

What the template does not make cheaper is the pictures. Every page needed its own set: product imagery chosen or made for that sector, interface captured and composed into the capability cards, each one specced and checked. That, not layout, is where a twelve week schedule actually goes, and it is the part that gets left out when people talk about shipping twenty eight pages.

• Fixed section order
• Hero speaks the sector's language
• Capability grid from real UI
• Reorderable sections
• Imagery made per page

The component library is not a flourish here, it is the delivery mechanism. A client editing pages in WordPress after handover cannot be asked to rebuild a layout, so the pieces they touch had to be small, named and repeatable: navigation, badge, button, feature card, statement band, capability card with a screenshot slot, testimonial, footer.

The capability cards carry real interface rather than icons. On a platform this abstract, a picture of the actual screen is the only thing that separates a claim from a promise, and it is the part a buyer scrolls back to.

• Named, reusable sections
• Real UI inside the cards
• Built for CMS handover