WooCommerce Multisite to October CMS + Meloncart - Architecture Check for Single-Warehouse, Multi-Region Store

eCommerce
#1

Hi there. We’re proposing a client migrates away from WooCommerce to October CMS + Meloncart and would love a sanity check on our proposed architecture.

1. What They Currently Have

  • Platform: WordPress Multisite + WooCommerce.
  • Fulfilment: One physical warehouse fulfilling a synced catalog across three storefronts:
    • Global (example.com/)
    • Australia (example.com/au/ )
    • New Zealand (example.com/nz/ )
  • Store Behaviour: Each regional sub-site has localised content, regional pricing/currency, and country-specific shipping options.
  • The Pain Point: Because WP Multisite isolates tables (wp_posts , wp_2_posts ), we rely on clunky database/webhook sync tools to keep inventory levels synchronised across the network, and it’s a pig to maintain.

2. What We Want to Achieve in October CMS

  • Move to a modern, maintainable Laravel/October foundation.
  • Preserve Local SEO: Maintain distinct, indexable regional routes (/ , /au/ , /nz/ ) with dedicated metadata, regional Product/Offer JSON-LD schemas, and automated hreflang tags.
  • Zero Inventory Sync Overhead: Fulfill from a single inventory pool in real time without background sync jobs, duplicate SKU rows, or cross-store webhooks.
  • Regional Rules: Display regional pricing and restrict shipping methods based on customer destination.
  • Regional Visibility Control: Ability to selectively exclude/hide individual products from specific country routes (e.g., if an item cannot be economically shipped to the US).

3. Our Proposed Approach

Rather than setting up 3 completely isolated Meloncart stores (which duplicates catalogs and brings back the stock-syncing problem), we plan to decouple October’s CMS Multisite routing from a unified Meloncart catalog :

  1. Multisite Routing Layer: Use October CMS core Multisite with CMS route prefixes (/ , /au , /nz ) under a shared domain to handle regional context and localised themes/content.
  2. Unified Catalog & Inventory: Maintain a single master product catalog in Meloncart. All regional storefront pages read from this same catalog and deduct from the same warehouse stock pool.
  3. Regional Pricing & Shipping: Leverage Meloncart’s currency and price rules for regional adjustments, combined with country-restricted shipping methods.
  4. Selective Product Hiding (Bridge Plugin):
  • Extend Meloncart’s Product model with an excluded_sites JSON column and a backend checkbox list.
  • Apply an Eloquent Global Scope to Product that automatically checks the active site and filters out restricted items from category listings and search.
  • Add a 404 guard on the product detail page and dynamically exclude restricted regional URLs from layout hreflang tags.

Questions:

  1. Has anyone run a single-catalog, multi-prefix setup like this with Meloncart and October Multisite?
  2. Are there any known caveats with Meloncart’s cart/checkout session handling or currency persistence when navigating between Multisite route prefixes?
  3. Does this single-catalog + global scope approach feel right, or is there a native Meloncart pattern we should look at instead?

Thanks in advance.