Reduce comparison ambiguity
Give agents stable product identifiers, variant relationships, price context, and policy references instead of asking them to infer facts from presentation pages.
← Platform
For retailers and catalog businesses
Current product data for shopping agents.
Lumeo publishes current product, offer, policy, and availability data from the systems that already run the business—then places explicit controls around quotes, carts, and orders.
Why teams make the change
A better interface creates better decisions before it creates automation.
Keep volatile facts current
Refresh availability and offers on a schedule appropriate to the source, and return an explicit unknown or stale state when certainty is not justified.
Separate intent from commitment
Let an agent research, check, and prepare while reserving purchase, refund, or account changes for the right authorization path.
Representative journeys
What a useful agent interaction looks like.
The request remains natural. The response and control boundary become explicit.
“Find a waterproof commuter jacket under €180 in medium.”
Structured candidates with variant IDs, current offer context, materials, and source timestamps.
Public or scoped catalog read“Is the navy version available for delivery to Berlin this week?”
A grounded availability result or an explicit unknown state—never a guessed promise.
Scoped real-time read“Prepare a quote for 40 units with company billing details.”
A reviewable quote request containing normalized SKUs, quantities, and the applicable policy version.
Owner approval before submissionSource authority map
Every answer should have an accountable owner.
Lumeo does not treat every page as equally authoritative. Each fact type can point to the system responsible for keeping it true.
SystemOwnsPublished as
Names, variants, specifications, media references
Canonical products and Markdown
Stock state, fulfillment location, availability time
Scoped availability tool
Regional offers, cart rules, order state
REST/MCP tools
Shipping, returns, warranties, purchasing terms
Cited policy resources
Tool patterns
Start narrow. Earn the right to automate.
search_catalogReadCatalog search
Returns normalized products and offers using explicit filters and stable identifiers.
check_availabilityReadAvailability
Queries the operational source with a narrow SKU, location, and time boundary.
prepare_quoteApprovalQuote preparation
Creates a reviewable action record before anything is submitted upstream.
Where the current experience breaks
Variants, regional prices, and availability are split across pages and client-side state.
A shopping agent can find a product but cannot tell whether the offer is current or authoritative.
High-intent actions fall back to brittle browser automation with unclear approval and payment boundaries.
What a controlled gateway changes
Canonical product and offer records with source provenance and observed times.
Fast, scoped catalog and availability tools that do not expose the underlying commerce platform.
Approval-aware quote or cart preparation before a person or authorized payment flow commits.
A responsible rollout
Move from readable to operational in controlled steps.
Publish the catalog
Verify the domain, connect one authoritative feed, and review product identity and offer precedence.
Add volatile reads
Introduce inventory or delivery checks with scoped credentials, limits, and freshness policies.
Control commercial actions
Map quote, cart, or order workflows only after schemas, idempotency, approvals, and payment boundaries are tested.
Questions worth asking
Clarity before commitment.
Does Lumeo replace the storefront?
No. The human storefront remains unchanged. Lumeo publishes a parallel machine interface backed by approved business systems.
Can an agent place an order automatically?
Only when the business deliberately publishes that tool and configures its authorization, approval, idempotency, and payment policy. Research and preparation can remain separate from commitment.
What should we connect first?
Usually the product catalog or feed with the clearest identifiers and ownership. Availability and transactions should follow after canonical product output is reviewed.
Begin with one source and one useful question