Platform Architecture Overview

Platform Architecture Overview

Applies To: [ All Licenses ]

Overview

This article explains how the Software platform is structured — how Hubs and storefronts relate to one another, how settings and catalog content flow downstream, and where each of the six license types fits in the overall architecture.


The Hub and Storefront Model

The Software uses a two-tier hierarchy: Hubs at the top, and child storefronts beneath them.

A Hub is the central control point. It owns the master product catalog, manages pricing, and can create and oversee one or more child storefronts. The Hub operator controls what content flows down to storefronts and when.

A child storefront is an independent customer-facing website that operates under a Hub. Each storefront has its own domain, branding, and customer base, but draws its catalog and pricing from the Hub above it.

This model allows a single Hub operator to run a network of storefronts. For example, a print company can white-label its ordering platform for multiple reseller clients, each of whom gets their own branded storefront without needing to manage their own products or pricing from scratch.


Catalog Inheritance and Sync

When a Hub publishes a product or pricing update, that change flows to child storefronts in one of two ways depending on the storefront's license type.

Auto sync (Auto Push and Basic Auto Push): Changes published by the Hub are automatically applied to these storefronts. The storefront operator does not need to take any action.

Manual push (Manual Push and Basic Manual Push): Changes are only applied when the Hub operator explicitly pushes them to the storefront. This gives the Hub operator precise control over the timing and scope of each update.

Storefronts can override certain settings locally — such as contact-level pricing — but the base catalog and pricing originate from the Hub.


Settings Inheritance

In addition to catalog content, storefronts inherit a range of configuration from their Hub, including:

  • Product catalog structure and option sets

  • Base pricing tiers

  • Shipping box sizes (configured at the Hub level)

  • Category structure and rankings

Storefronts can customize their own appearance, domain, branding, and certain pricing overrides independently of the Hub.


Where the Six License Types Fit

License Type

Tier

Position in Hierarchy

Catalog Sync

License Type

Tier

Position in Hierarchy

Catalog Sync

Hub

Full

Top — controls child storefronts

Publishes to storefronts

Auto Push

Full

Child storefront

Receives auto sync from Hub

Manual Push

Full

Child storefront

Receives manual push from Hub

Basic Hub

Basic

Top — controls child storefronts

Publishes to storefronts

Basic Auto Push

Basic

Child storefront

Receives auto sync from Hub

Basic Manual Push

Basic

Child storefront

Receives manual push from Hub

Full-featured licenses (Hub, Auto Push, Manual Push) have complete ecommerce functionality — full catalog activation, Online Designer, Corporate Portals, custom CSS and JS, and all payment and shipping options.

Basic licenses (Basic Hub, Basic Auto Push, Basic Manual Push) have limited ecommerce functionality. The catalog is not fully activated and site capabilities are restricted. Basic licenses are typically a starting point before upgrading to a full-featured tier.


A Typical Network Example

A Hub operator runs one Hub license and three child storefronts:

  • Two storefronts on Auto Push — they receive catalog updates automatically whenever the Hub publishes.

  • One storefront on Manual Push — the Hub operator pushes updates to this one on a controlled schedule.

Each storefront has its own domain and branding. Customers on each storefront see only that storefront's products and pricing. All orders flow back into the Hub operator's admin for production management.


Notes / Tips

  • A Hub can manage an unlimited number of child storefronts. Contact your Account Sales Manager (ASM) regarding storefront licensing.

  • Basic Hub licenses can manage child storefronts but have restricted ecommerce capabilities on the Hub itself. The child storefronts they manage can be any license type.

  • Storefronts cannot manage other storefronts — only Hub and Basic Hub licenses have that capability.


Related Articles