Product foundation
One dependable source of store information.
- Product identities and variants
- Price, stock and buying policies
- Structured records for each journey
One store.
For people and
their agents.
One accurate store understanding. Two ways to buy.
Discuss a pilotNullstar CommerceProduct concept
Merchant source
One accurate store model.
- Identity
- Products & variants
- Offer
- Price & availability
- Conditions
- Delivery & returns
- Context
- Language & approved content
For people
A relevant page.
Merchant-approved emphasis
For agents
Facts and actions.
Customer-authorized purchase
Commerce changes.
The store stays true.
The product thesis
- One foundation
- Accurate store facts
- Human Commerce
- Merchant-approved relevance
- Agent Commerce
- Supported actions + customer permission
Different interfaces. The same accountable source.
The Nullstar Commerce approach centers on one store understanding for relevant human experiences and supported, customer-authorized agent journeys. People browse pages. Agents work with structured facts. Both need to understand the same products.
Today, campaign intent can disappear at a product page. An agent can struggle to establish the facts and actions a store actually supports. We connect those problems through one merchant-grounded model of product identity, variants, price, stock, delivery and policies.
Our first useful wedge is Nullstar Match: one campaign-to-product journey shaped around shopper intent, using content approved by the merchant. It gives us a narrow place to test the model before expanding agent capabilities.
A focused pilot starts with a real merchant, a specific buying problem and clear evidence to review together.
The same product.
A different way to understand it.
Keep the reason behind the click, the facts behind the store and the permission behind every action connected.
Nullstar CommerceProduct concept
Merchant source
One accurate store model.
- Identity
- Products & variants
- Offer
- Price & availability
- Conditions
- Delivery & returns
- Context
- Language & approved content
For people
A relevant page.
Merchant-approved emphasis
For agents
Facts and actions.
Customer-authorized purchase
One foundation.
Two buying journeys.
Connect accurate store information to merchant-approved pages and customer-authorized agent tasks.
Merchant experience
Relevant pages with merchant control.
- Campaign intent and page emphasis
- Merchant review and approval
- A focused comparison against the current journey
Agent journeys
Clear information, scope and permission.
- Storefront access and integrations
- Supported actions and verifiable results
- Explicit customer authorization before purchase
What needs to be
proven next.
Start with a real store and a limited question. Let the evidence shape what we build next.
- 01
Ground the store
Review product identities, variants, prices, stock and buying policies with a merchant.
Evidence to seekA reviewed store model
- 02
Test the human journey
Scope a Nullstar Match experiment around one campaign and one product group. Compare an approved variation with the current experience.
Evidence to seekA baseline and a focused experiment
- 03
Validate one agent task
Select a storefront, an agent interface and a limited task. Test access, failures and the customer authorization boundary.
Evidence to seekA documented supported flow
- 04
Learn before expanding
Use the results to decide which integrations, monitoring and recurring product capabilities should come next.
Evidence to seekEvidence for the next build
Trust has to survive
a new shopping interface.
Facts stay grounded
Relevance can change a page’s emphasis. It cannot invent a benefit, a price or availability.
People keep control
Merchants approve content changes. Customers review and authorize purchases.
Support needs evidence
Compatibility is established for a specific platform, agent and journey. Access alone does not prove a transaction.
One store stays consistent
Human pages and agent interfaces use the same merchant facts, with language and interfaces suited to the actual store.
One store is enough to start.
We’re looking for merchants and design partners with a concrete buying problem to test.
Discuss a pilot