Nullstar CommerceDiscuss a pilot
Agent Commerce

A different buyer.
The same store.

Give shopping agents accurate store facts and supported actions, with customer permission before purchase.

Discuss a pilot
Nullstar CommerceProduct concept
A customer’s request

“Find the right option. Check the conditions. Ask me before buying.”

  1. 01
    DiscoverReach the correct product record
  2. 02
    UnderstandRead variants and buying conditions
  3. 03
    PrepareUse one supported action
  4. 04
    Customer authorizationReview the action before purchase
Illustrative architecture.

Find the right product

Provide accurate public records and test whether a selected agent can discover the relevant item.

Understand the store

Keep product details, variants, availability and buying conditions connected to the same merchant source.

Act with permission

Prepare supported actions and require explicit customer authorization before a purchase proceeds.

Explore the agent buying journey.

Four capabilities. Each needs its own test.

Capability to verify

Can a relevant agent find the product?

Give the product an accessible public identity. Then test whether the selected agent can reach the correct record.

Evidence to inspect
Public product pages, access rules and discoverable records.
A concrete test
Find the intended item from a specific shopping request.

Public access does not guarantee indexing or a recommendation.

Reading a store is only the beginning.

Discovery, understanding, preparation and purchase require different evidence. One successful layer does not prove the next.

Evidence required to verify each intended agent commerce capability
Evidence to verifyDiscoverUnderstandPreparePurchase
Public product identityRequiredRequiredRequiredRequired
Consistent variants and specificationsUseful contextRequiredRequiredRequired
Current price and availabilityUseful contextRequiredRequiredRequired
Delivery and return conditionsUseful contextRequiredRequiredRequired
A supported action interface——RequiredRequired
Explicit customer permission——Defined scopeRequired
Verified payment and order result———Required

A verification framework for a selected integration. Support must be tested for the specific agent, platform and buying journey.

Shared store foundationProduct concept

Facts with a clear source.

Identity
Product + selected variantCatalogue
Offer
Current price + availabilityMerchant source
Conditions
Delivery + return policiesStore policies
Context
Approved product informationMerchant review

Presentation can change. Product facts and buying conditions stay grounded.

Illustrative record. No merchant data is connected.

Make the facts
understandable.

The agent needs a consistent account of what the merchant sells and the conditions of buying it.

  • Connect the product to the correct variant.
  • Keep price and availability current.
  • Make delivery and return conditions clear.
  • Verify the selected agent interprets the record correctly.

The customer
authorizes the purchase.

Preparing a cart is not permission to buy. A supported purchase needs a reviewable product, quantity, total, delivery and action scope.

  • Present the intended action clearly.
  • Obtain the customer’s required permission.
  • Use a compatible payment and order flow.
  • Verify the resulting order before reporting success.
Review before purchaseConcept
Selected action

Review the intended purchase.

Product + variant · Quantity · Total

Price & availability
Current merchant source
Delivery
Verified at checkout
Permission
This reviewed action only
Payment
Supported, authorized flow

Concept only. No order is prepared or placed.

A narrow journey.
A result we can verify.

Start with one merchant, a selected agent and a specific shopping request. Prove each required step before expanding.

A focused integration test

One request.
A clear result.

Input
A specific customer task
Source
Merchant-grounded facts
Boundary
Supported, permitted action
Result
Evidence to verify
“Find the right option. Check the delivery conditions. Ask me before buying.”

Define the product source, the supported action interface and the customer’s authorization model together.

The useful outcome is evidence: the correct record, the correct action and, where a purchase is supported and approved, a verified order result.

Explore the readiness assessment

Merchant control

The store defines product truth and the actions it permits.

Customer scope

Permission covers the reviewed action through a supported flow.

A verifiable result

Confirmed outcomes are distinct from prepared or unsupported actions.

Choose what
supports the journey.

Public records, merchant feeds, storefront APIs and agent tools can serve different parts of the flow. The integration follows the use case.

Support depends on the agent, platform, payment flow and authorization model.

Discuss a pilot

Understand the next
step for your store.

Explore the assessment, the shared foundation and the first pilot conversation.

Assessment

Review your store’s readiness

Understand the observable evidence and the limits of a public assessment.

Foundation

Explore the shared store model

Connect the same merchant facts to human experiences and intended agent paths.

Pilot

Discuss a focused integration

Bring one store and one buying journey to scope and verify together.

Make one agent journey verifiable.

For merchants and platform partners exploring a focused integration.

Discuss a pilot