Make the record once. Dispatch it everywhere.
Canonical product identity, media, and commerce basics stay coherent while each storefront chooses its own expression.
Z9 / Catalog core
One library.
Ready to go.
Z9GO is the product utility behind the storefront network — canonical items, house names, and site links, dispatched once so every shop can stay selective.
Private by design / operators only / not a consumer catalog
catalogcore
StorefrontsHouse namesMediaSite links02 / The shape of the system
One quiet core. Many sharp storefronts.
The public page stays high-level on purpose. The useful work—catalog memory, network links, and operator tools—begins after sign-in.
Keep the messy work off the public page.
Operators see network health and library coverage in a focused workspace—not in a public data dump.
03 / Operating principles
Built for the part nobody sees.
Z9GO is the utility behind a family of commerce experiences. It should feel exact, calm, and ready for the next network.
Identity first.
Network + external identity + marketplace keeps records durable as the library grows.
Selection stays local.
Shared knowledge does not flatten the house voice of the storefront using it.
Access is deliberate.
Google operators and authenticated APIs keep the control plane private by default.
04 / Why a catalog core
Jobs that used to live in every shop.
Z9GO exists because a family of storefronts kept solving the same product problems in parallel. These are the tickets it takes off each site’s plate.
Case / 01GO
Open the next shop without copying a catalog.
A new storefront should not start by pasting marketplace titles into a new repo. It attaches to the library, picks what belongs on its shelf, and keeps its own slugs and house names.
Case / 02HOLD
Share the facts. Keep the voice.
The same item can sit in more than one shop. Listing identity, gallery, and commerce basics live once. Each site still names the product the way its shoppers talk — short house names, not shipping-label titles.
Case / 03CHECK
Check health once. Dispatch only what can go.
Dead listings used to linger because every site checked on its own schedule. The core verifies availability, holds what failed, and lets storefronts pull a catalog that is allowed to go. Shops do not scrape the marketplace from a datacenter and call that health.
Case / 04STOP
Retire a dead link without a fleet of deploys.
When something falls off the network, an operator marks it from the deck. Syndication stops. You do not need a pull request in every storefront just to take a product off the shelf.
Case / 05NEXT
Leave room for the next commerce network.
Identity is network, external id, and marketplace — not an Amazon-only spreadsheet. Amazon is first. The same plate can take another network later without rewriting the model.
Operator access / next move
Open the deck when you are ready to work the library.
Sign in with an allowed Google account to enter the private control plane.
Sign in with Google ↗