Documentation menu

/

Get started

How Neomi connects

The architecture of the integration, and the three things it deliberately is not.

The most common misunderstanding about Neomi is that it installs into your storefront. It does not, and the difference matters for scoping.

A separate storefront, not a layer on yours

Neomi runs as its own AI storefront alongside your existing online store. It does not install into your storefront platform, and it does not require that platform to be extensible. If your storefront is locked down or controlled by a third party, that has no bearing on whether Neomi can run.

It reads your data through defined interfaces

Catalog, inventory, pricing, cart, and orders, each scoped to what a storefront needs to function. Access is granted per domain rather than as one blanket connection, so you can start with the minimum and extend later.

The order comes back to you

Neomi assembles a cart and hands it to the checkout you already operate. Payment, fulfillment, and the order record stay in your systems. Neomi does not take the order.

What this is not

  • Not a plugin into your storefront platform, and not dependent on it being extensible.

  • Not a replatform. The store you run today keeps running exactly as it does.

  • Not a new system of record. Your catalog, orders, and customers stay authoritative.

Diagram

Documentation in progress. Our engineering team publishes this section with the reference.