Frequently asked questions

The questions engineers ask before scoping an integration. If yours is not here, the answer is a conversation rather than a page.

Does Neomi replace our storefront?

No. Neomi is a separate storefront that runs alongside the one you already operate. Both point at the same catalog and the same checkout. Nothing is installed into your current storefront platform.

What access does Neomi actually need?

Read access to the domains a storefront needs to function: catalog, inventory, pricing and promotions, plus an interface that accepts a completed cart. Loyalty and purchase history are optional and only improve personalisation.

Who takes the order and the payment?

You do. Neomi hands the cart to the checkout you already run, so payment, tender types, fulfillment, and the order record never leave your systems. Because that flow is untouched, whatever your checkout supports today keeps working.

Do you write anything back into our systems?

Neomi places orders through the interface you expose, and that is the extent of it. It does not modify your storefront and does not become a system of record.

Can we start with a subset of the domains?

Yes, and most pilots do. Catalog, inventory, pricing, and cart are the minimum for a working storefront. Loyalty and merchandising can be added later without revisiting the earlier work.

What happens with dietary and allergen data?

Neomi reads whatever dietary attributes your catalog carries and can enrich the tags that are missing. To be clear about what that is: better tagging and filtering, not a medical or allergen guarantee.