Catalog and PIM

Everything a shopper can ask for has to resolve to a real product in your catalog. This module is how Neomi reads that catalog and keeps its understanding of your assortment current.

What Neomi reads

• Products, with the identifiers you already use.

• Attributes, including size, unit, and pack information.

• Category structure, so requests can be narrowed the way your merchandisers think about the store.

• Dietary attributes where they exist. Where they do not, Neomi can infer and enrich them rather than asking you to fix your product data first.

What stays in your systems

The catalog remains authoritative on your side. Neomi does not edit your product records, and any enrichment it derives lives on the Neomi side unless you ask for it back.

How to connect

Most grocers already expose a catalog feed or an API for their existing storefront. If yours does, that is usually the starting point.

• Agree the scope of this domain and the locations it applies to.

• Expose the interface, or point us at the one you already run.

• We validate against a non-production environment before anything goes live.

Data expectations

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

Errors and edge cases

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

Reference

The endpoint reference for this module is published here when it is finished. Until then, nothing on this page describes a specific interface, because we would rather leave it blank than have you build against something that changes.