Books run on catalog. Build the shelf.

Publishing metadata travels in ONIX 3.1, an XML schema maintained by EDItEUR. ONIX contains ISBN, title, contributor roles (author, editor, illustrator, translator), format, street date, publisher, imprint, BISAC subject codes, audience, jacket copy, cover image URLs, price, and distribution rights. It is the standard every distributor, wholesaler, and library uses.

The ingestion pipeline pulls ONIX from your distributor (Ingram, Baker and Taylor, PGW, Consortium), parses the XML, and maps each field to a Shopify product metafield or variant attribute. Weekly scheduled runs keep the catalog current; ONIX update feeds handle price changes, cover art updates, and street-date moves without human touch.

For self-distributing publishers, ONIX often comes from the title-management system (Biblio, Klopotek, Firebrand) rather than a distributor. Either way the pattern is the same: ONIX is the source of truth, Shopify is the storefront, and the ingestion pipeline is the bridge. Stores skipping ONIX and hand-entering titles lose 3 to 10 hours per title and introduce inconsistencies that break library-facing data exports later.

Book buyers pre-order weeks or months ahead of publication. Charging at order is the default Shopify behavior; it breaks for pre-orders because the customer expects to be charged close to delivery. The technically-correct pattern: Shopify Draft Order created at purchase, payment method stored via Shopify Payments, scheduled job fires on publication date to convert the draft into an invoice and capture payment.

Implementation runs about 2 to 3 weeks of engineering on top of a base Shopify build. The scheduled job is a Cloud Run service (or Shopify Flow with a custom app trigger) that fires nightly and processes any pre-orders with pub date in the next 24 hours. Pre-order cancellation handling, card-expiration checks, and refund-before-ship windows all live inside the same service.

For publishers running subscription programs (book-of-the-month, first-edition clubs) on top of pre-orders, Recharge handles both patterns with a single subscription configuration. See our subscription app comparison for Recharge vs Skio decision context.

For most publishers and indie bookstores, 30 to 50 percent of total revenue comes from trade accounts: libraries, schools, universities, corporate gift programs, book-clubs, and other retailers buying for resale. Trade buyers operate on net-30 terms, expect volume discounts, need invoice-based billing rather than credit card, and often require approval workflows on their side before orders release.

Shopify Plus B2B covers most of these needs natively. Company accounts with multiple buyers per account, catalog-level pricing rules that apply automatically when a trade buyer logs in, draft-order approval workflows, net-30 invoicing via Shopify Payments or integrated with the publisher's existing AR system. For non-Plus stores, Shopify Wholesale (the legacy channel) still works but has fewer features.

The trade portal is typically a dedicated subsection of the main site (trade.yourpublisher.com or yourbookstore.com/trade) behind login. Same catalog, different pricing, different checkout flow. For publishers with 500K-plus annual revenue from trade, this is where the next growth comes from - and where most Shopify migrations underinvest.