Do I need a cannabis license to partner with CommerceOS?

Yes. CommerceOS only works with licensed cannabis retailers in legal states. The retailer remains the license holder of record; CommerceOS is the delivery channel and software layer. A state-issued retail or delivery license and an approved menu feed are the starting requirements.

Who handles customer support — CommerceOS or the retailer?

Support ownership is defined in the launch agreement. Default split: CommerceOS owns delivery ops, order status, driver support, and platform issues; the retailer owns product questions, promotions, and loyalty. The handoff is visible to customers — they always know who to contact.

How does menu sync work?

We connect to your POS through an approved integration (Dutchie, Treez, Flowhub, Jane) or a read-only feed. Inventory, pricing, and product data stay in your system of record; CommerceOS mirrors them with low-latency sync. Deals, loyalty, and coupon logic can run on either side per contract.

Do customers see my store identity, or is it a generic marketplace?

Every partner storefront is branded to the retailer. Name, logo, identity, delivery zone, and support owner are visible early — before checkout. No generic marketplace routing. Customers always know which store they're shopping and who fulfills the delivery.

What's the launch timeline for a new retailer?

Typical launch lands inside 30 days from signed agreement: week 1 store setup and service area, week 2 menu sync verification, week 3 dry-run and ops alignment, week 4 public launch. Pending-menu stores can be prepared earlier as clearly labelled pending storefronts, but public launch waits for a usable menu and delivery ops.

What states does CommerceOS operate in today?

Massachusetts is the launch market. The compliance engine and software stack are built for state-aware expansion, but State-by-state expansion follows retailer readiness and local delivery approval.

What does it cost to partner with CommerceOS?

A monthly platform fee plus a per-delivery transaction fee. No setup cost for the standard launch package. Custom payments, headless API access, and multi-store rollups are priced per deal. Email contact@jalenbuilds.com for a full quote — pricing is disclosed before a contract.

Retail Growth Layer

The new standard for licensed delivery channels.

Launch a branded delivery channel in the CommerceOS network. Reach Massachusetts customers. Grow with us.

Inquire now Explore platform demo

Licensed menus onlyIntegrated dispatchReadiness-based demand

Market Placement

Launch market

Boston

One clean retailer storefront proven before we broaden.

Active cities

12 live cities

Explicit coverage so promises stay grounded.

Next wave

Worcester, Springfield, Lowell, Cambridge

Market-by-market expansion as retailers and delivery are ready.

Strategic progression

Built to launch cleanly. Designed to expand when ready.

A branded storefront today. Full platform later.

Phase 1

Embed-first launch store

A branded storefront around your hosted menu. Customers browse, order, and get delivery.

Fast launchHosted menuStable public URL

Phase 2

Operational visibility and sync

Better support, status visibility, and menu/payment reliability.

Status visibilitySupport clarityUpgrade path

Phase 3

Full platform integration

Custom reporting, deeper commerce tools, and headless-ready integration when the lane has earned it.

Headless readyCustom reportingReadiness-based expansion

The Launch Package

What we stand up in your first launch store.

Not a menu embed. A storefront with service areas, support, and analytics.

Stable public URL

Branded storefront shell

A retailer-specific CommerceOS lane launches on a stable slug with store identity, category-first entry points, and local trust markers before the customer ever sees checkout.

Embed-first or synced

Approved menu connection

The live menu path is wired through the right commerce mode so the lane can launch quickly without pretending CommerceOS owns more of the transaction than it actually does.

Market truth

Service-area confidence

City, neighborhood, and eligibility guidance stay explicit so CommerceOS only sends shoppers into lanes that are genuinely serviceable today.

Operational trust

Support and compliance posture

Age-gate expectations, delivery support ownership, and handoff boundaries stay visible near the path to order instead of disappearing behind the menu.

Demand proof

Attribution and upgrade path

CommerceOS starts tracking storefront sessions, menu starts, and discovery exits immediately so the relationship can graduate into deeper sync, API, or headless access with real evidence.

What we prove first

We earn trust before asking for deeper access.

Real demand, not promises.

Signal 1

Storefront sessions

CommerceOS can prove that real shoppers reached a retailer-specific lane instead of generic directory traffic.

Signal 2

Menu-start intent

CommerceOS can show which stores, entry points, and discovery surfaces turn browsing into actual menu openings.

Signal 3

Discovery spillover

CommerceOS can measure when shoppers need more research or leave for related discovery surfaces, which makes partner improvements concrete instead of vague.

Signal 4

Upgrade leverage

Once a lane is generating measurable demand, CommerceOS has the proof it needs to ask for better API, webhook, and headless access from the strongest partners.

Live Network Proof

Review our launch-market coverage.

Open the live storefront, the demo, and the coverage map.

Review a live storefront

See how it looks for customers before the conversation gets technical.

Open live storefront

Walk the guided platform story

Walk the CommerceOS story in order, then move into the admin workspace for proof.

Open guided demo

Inspect active delivery coverage

Current launch cities and active service areas.

View delivery coverage

Customer Experience

A retail storefront that leads with browsing and trust.

Clear store identity, clear path to checkout.

Storefront Preview

Category-led discovery

Live Status

Customer discovery

Category-led browsing

A storefront, not a raw feed. Categories, specials, and delivery context up front.

FlowerPre-rollsEdiblesVapes

Retail trust

Location and zone clarity

Availability, territory, and identity — clear before cart.

BostonCambridgeBrookline

Conversion confidence

Trust before checkout

Age-gate, support, and delivery terms near the buy flow — not the footer.

21+ gateLive supportHandoff proof

Identity & Clarity

Customers always know which store they're shopping.

Retailer identity and delivery model visible early.

Retailer slugDelivery zoneSupport owner

Trust Infrastructure

Age verification before menu access
Delivery support language near the CTA
Handoff expectations before checkout

Retailer Outcomes

More than a menu embed.

Operationally complete \u2014 not a storefront that hands customers off.

A storefront built around your menu

Your own page on the network, powered by your live menu.

Delivery support behind the customer flow

Real delivery ops, customer support, and status visibility.

Retailer-facing visibility

Orders, routes, and support in one place.

Best first launch

Start with one clean launch. Expand when it's proven.

What this avoids

Generic marketplace routing. Fractured support. Unclear delivery ownership.

Retailer outcome

A branded delivery path customers trust — no rebuild required.

Fit Check

Strong first fit beats a broad but shaky launch.

The right launch is specific, supportable, and honest.

Optimal Launch Fit

Want delivery that feels native, not outsourced.
Ready to launch in Massachusetts first, then expand.
Want clear ownership of support, compliance, and customer experience.

Not the right launch yet

No approved menu feed yet.
Want statewide promises before city-level readiness.
Want a generic marketplace without delivery accountability.

Getting started

How we launch your store.

Set up your store

Confirm store details, service area, and menu source. Go live when ready.

Connect your menu

We verify your inventory feed and make sure customers see accurate, real-time products.

Grow together

Once live, unlock deeper analytics, support tools, and storefront customization.

Honest store status

Customers always know what they're getting.

Demo, pending, and live stores are labeled clearly. No guessing whether a menu is real.

Demo

Sales/demo lane only. Do not position as a live partner menu.

Bridge lane

Catalog is visible through an approved bridge, not a first-class provider sync.

Pending menu

Partner lane exists, but no supported menu connection is ready yet.

Live menu

An official menu path is healthy enough to position this partner as live.

Integration maturity

We only call a provider live when it is actually usable.

Today, Dutchie is a live menu provider. Your store can still launch while Weedmaps, Treez, Jane, Flowhub, BLAZE are still being integrated.

Dutchie

Live

Primary live menu sync lane for partner storefronts and inventory refresh.

Production-capable and safe to position as an active platform lane.

Weedmaps

Stub

Discovery and API groundwork only. Not an approved live sync lane yet.

Credentials or models may exist, but the integration is not operationally ready.

Treez

Stub

Provider placeholder only. Treez menu sync is not production-ready.

Credentials or models may exist, but the integration is not operationally ready.

Jane

Stub

Provider placeholder only. Jane seller sync is not production-ready.

Credentials or models may exist, but the integration is not operationally ready.

Flowhub

Stub

Provider placeholder only. Flowhub sync is not production-ready.

Credentials or models may exist, but the integration is not operationally ready.

BLAZE

Stub

Partner-API scaffold only. BLAZE Retail sync requires approved partner access, OAuth credentials, and a production inventory + manifest path.

Credentials or models may exist, but the integration is not operationally ready.

Stripe

Live

Primary card payments, saved methods, and billing foundation.

Production-capable and safe to position as an active platform lane.

Aeropay

Beta

Bank-payment code paths exist, but the lane is not positioned as launch-ready.

Partially implemented. Do not position as fully launch-ready without verification.

Email provider

Live

Transactional email delivery for customer and operator notifications via Brevo, Postmark, or Resend.

Production-capable and safe to position as an active platform lane.

Twilio

Live

SMS updates for assignment and order state changes.

Production-capable and safe to position as an active platform lane.

METRC

Stub

Compliance groundwork exists, but METRC is not yet a production-ready operational lane.

Credentials or models may exist, but the integration is not operationally ready.

ID verification

Planned

Future vendor abstraction for identity and age verification.

Roadmapped only. No supported runtime lane yet.

Launch expectation

You can launch on a temporary menu bridge if your POS integration isn't live yet. We only mark a store "live" when the menu and delivery ops are genuinely usable.

What we need

Clean inputs. Faster launch.

No need to replace anything on day one. A clean menu path, store identity, and support agreement.

Read-only menu access or an approved POS connection
Your store URL and branding for your public page
Alignment on promotions, loyalty program, and who owns support
Optional inventory webhook or sync frequency once POS access is live

Territory

Current Massachusetts cities first, then outward by retailer readiness

Loyalty path

Retailer-compatible promos, referrals, and optional loyalty hooks

Next step

If you already operate a menu, we can talk now.

Reach out for the retailer packet and launch plan. We'll walk through your setup and how your store goes live inside CommerceOS.

Email retailer team See the customer view

Retailer inquiry

Tell us about your store.

Share your details and we'll send partnership info.