Eden capabilities

Full capability list for Eden.

Last updated: July 14, 2026

This page is the “what can Eden answer?” reference for Eden.

Short answer to the popup question: the plus-menu starters are only a curated starter set, not the full capability surface.

How to read this list

Deterministic (facts-first): Eden uses allowlisted facts sources and does not rely on model generation for the final answer.
Model-assisted: Eden uses governed facts context plus model interpretation for broader open questions.

Eden is local-first. Model-assisted replies run through ChannelWeave’s controlled local model environment, not a hosted model API. When Eden does not recognise an operational question through the deterministic router, it makes one local structured intent-classification pass. That classifier can choose an allowlisted intent only; it does not generate facts or answers. If the classifier does not return a valid supported intent, Eden falls back to the existing governed model-assisted answer path.

Eden also appears contextually in selected app workflows. App page help uses an Eden leaf icon instead of a generic question mark; it opens page-aware Eden help with the exact current guide, a clean input, and suggestions that are valid for that page. Which warnings matter? appears only where the linked guide defines checks, warnings, or attention states. Known page-help requests bypass the general intent classifier: the server resolves the allowlisted guide and grounds the answer in that guide instead of guessing from the prompt. The page-help suggestions keep the useful page and account guidance and remain available after Eden replies, so the user can choose another starter without closing the modal. Page-help starter answers are transient until the user types a follow-up; if the user does continue, ChannelWeave saves the starter exchange with the follow-up under a page-aware title. Follow-ups carry a bounded recent conversation window, whether the modal is still transient or the conversation has been saved, so Eden can resolve short references such as “what about the next one?” without receiving an unbounded transcript. When the user opens full-page Eden from the modal, Eden shows the same suggestions and a Back to {page} link to return to the original task. Greetings only ever use the authenticated ChannelWeave user's name — never buyer names, page examples, or public artefacts. Eden also receives plain-English metric labels so answers should not expose raw field names. On Import stock, the page-help suggestions are also state-aware after validation: they cover the file summary, Location + Bin destination, Reference fact source, and the first grouped validation errors or warnings. Eden treats stock-import warnings as non-blocking when validation shows 0 blocking errors and can explain repeated policy warnings such as missing manufacturer barcodes without requiring the full validation report first. On Stock item forms, Eden suggestion chips send a short user label plus typed current-record context, so deterministic replies use the stock item’s latest quantities, reorder settings, catalogue readiness, and reference facts instead of trying to infer the page from the wording alone. The guided catalogue-readiness suggestion keeps that context across follow-up turns and can save a missing sale price only after the user replies with an explicit Apply confirmation. Eden then refreshes the stock item field in the open form, can draft and explicitly apply the default listing description, and guides the next readiness step. Eden conversations are persisted only after the first message, and users can delete saved conversations from the conversation list. In Inbox → Messages, eligible eBay and Website reply composers include Ask Eden, which drafts plain-text buyer reply copy from the recent conversation context. This uses a dedicated reply-drafting flow, separate from general Eden questions. Buyer and seller message bodies are fenced as untrusted text before the model sees them, so Eden treats them as context for the draft rather than instructions to follow. The draft is inserted into the composer only; Eden does not send buyer messages.

Stock and listing-draft description fields also use contextual Draft with Eden drafting. In stock and draft forms, the Draft with Eden and Add reference facts actions sit on the title row, then the title and description fields appear underneath. Those requests use a dedicated listing-description draft mode built from structured stock/listing facts, so description drafting remains separate from general Eden onboarding or daily-brief questions. Listing description drafts preserve explicit limitation, edition-size, numbering, serial, signature, certificate, included-item, dimension, material, compatibility, and condition-neutral specification facts when those details are present in the provided inputs. Wording may vary between drafts, but factual content must stay stable and limited to supplied buyer-visible facts. Eden must not add unsupported collectability, rarity, fan-demand, fulfilment, shipping, or packaging claims, and source-only metadata such as source URLs, evidence, database IDs, and release IDs is not used as buyer-facing copy. When a form offers Add reference facts, ChannelWeave fetches the page server-side, streams the response through a stripper that discards normal scripts, styles, links, comments, and other non-content blocks while preserving JSON-LD Product data, then extracts candidate facts from structured Product data, metadata, and page text. Common page-section headings are filtered before the remaining facts are shown for user approval. Eden receives only the approved facts, not the raw page; users can draft immediately from the selected facts or clear them before using Eden. If the product or listing title is still empty and the fetched page includes a product-name fact, ChannelWeave offers a separate Use as product/listing title action; Eden does not silently fill required title fields. Reference-page capture reads up to 2 MB of remote HTML and keeps up to 1.25 MB of stripped page content.

On stock items, Explain readiness issues is the advice-only catalogue readiness prompt. Fix readiness with Eden is the guided action prompt that can ask for a value, show inline action buttons for the proposed change, and apply only the change the user confirms. Page-help suggestion chips and plus-menu starters send immediately when clicked, so complete advice prompts do not need a second composer send step. Page-help chips stay visible for another quick question after the answer.

Capability coverage is governed internally before it is presented as supported behaviour.

Deterministic capabilities (facts-first)

1) Profile and orientation

Greeting responses (hello, hi)
Thanks acknowledgements (thanks, thank you Eden)
Today, yesterday, and tomorrow date questions, answered deterministically in the browser's validated time zone without a model call
Identity (who are you?)
Signed-in account identity (what is my name?, who am I?)
Light human acknowledgements (it’s my birthday, I’m stuck)
ChannelWeave overview (tell me about ChannelWeave)
Capability summary (what can you do?)
Beginner first-step guidance (What should I do first?) that can use the signed-in setup checklist to list remaining items in priority order
Setup confidence guidance (Am I set up properly yet?)
First channel/stock sequence guidance
Healthy connection and sync-check guidance
Signed-in plan and billing-status orientation from account context
Billing-management routing to Settings and Stripe billing controls
Clean channel-disconnect guidance based on the channel connection contract
Safe-click, undo, real-data action, team/customer visibility, and permission guidance
Main-area and core-term explanations for Control Centre, Inbox, Sales, Inventory, Listings, Eden, channels, connections, listings, orders, and stock items

Eden’s tone standard is warm precision: corporate-grade, calm, human, and concise. Eden should understand casual chat without mirroring nicknames, gendered labels, flirtation, or personas, and does not volunteer gendered identity in customer-facing answers. Eden avoids corporate filler such as “I’m happy to assist with your query” and moves the user towards the next ChannelWeave task.

Greeting and thanks responses may use one subtle Eden mark (✦). When ChannelWeave provides the signed-in user’s first name, greeting-only replies may use it, for example: “Hi Graham — how may I help you? ✦”. Safe direct greetings to Eden may adapt the salutation, for example “Hey Eden” can return “Hey Graham — how may I help you? ✦”. Longer operational answers that open with the signed-in user’s name should use Hi {firstName}, unless the user explicitly opened with “Hey Eden”. Casual greeting variants such as “hey girl” resolve to the same professional “Hi” greeting and are not mirrored back. Operational guidance does not use emojis or decorative marks unless the user explicitly asks.

Signed-in account identity answers use only the current user profile fields passed by ChannelWeave: first name, last name, and account name. Eden does not expose the user email in these answers, does not guess identity from chat text, buyer names, reply drafts, page visuals, examples, or public artefacts, and does not persist “my name is …” messages as profile changes.

Light human acknowledgements stay task-facing. For example, “it’s my birthday” can receive a brief birthday acknowledgement before asking what the user wants help with in ChannelWeave, while “I’m stuck” asks what task the user is trying to complete. When Eden and linked docs do not unblock the next step, users can open Ask the ChannelWeave team from Eden surfaces to create a lightweight in-app support request.

2) Docs-backed operational guidance

Concepts: stock groups, stock
How-to guidance: channels/shipping, stock, listings, orders, warehouses, sync queue/health, rules/automation, intelligence engine
Troubleshooting: common issues, channel connection issues, listings-import issues, orders-import issues

3) eBay listing-seed helper

eBay category/required-aspect prefill suggestions from title seed prompts

4) Stock items and stock groups

Stock item count (how many stock items?)
Stock item listing/search by name/SKU
Stock item listing by exact stock-group code or name
Stock-group count (including scoped name filters)
Stock-group naming/listing (single, numbered list, ordinal)
Duplicate stock-group-name checks
Stock-group stats:
- Exists / distinct names / distinct codes
- Latest/earliest created or updated/activity timestamps
- Top/bottom/average/min/max stock-item counts per group
- Created/updated change totals in an explicit date range
Stock-group sales ranking (best-selling/top by units/revenue)
Colloquial range/category sales phrasing such as ranges flying out the door
Stock-group aggregate parser:
- Aggregate functions: count, sum, avg, min, max
- Metric filters with and/or logic and optional exclusions
Stock-group sales change drivers:
- Deterministic paired-period comparison
- Top stock-group deltas

5) Operational risk checks

Daily operations brief for prompts such as How did it go today?
Bounded read-only operational plans for natural requests such as Put today's work in priority order, using at most three steps from the daily fact pack
Low-stock list and low-stock count
Low-stock scoping by location/warehouse
Colloquial low-stock phrasing such as stock lines the user should reorder
Sync-error summary (recent period)
Sync-error scoping by channel/source
Custom insight rule summary (active or paused, warning or fail state, open findings)
Colloquial insight-rule phrasing such as watchdogs or alerts going off
Custom insight rule detail (thresholds, current state, latest finding, template-specific evidence)
Exact stock-item lookup by SKU, including on-hand, allocated, available, and reorder quantities
Item-level sales ranking by units sold or revenue
Channel connection status, last successful sync/probe signal, recent failures, and connection attention state
Fulfilment queue lists for overdue, due-today, or due-or-overdue orders
Inbox threads where the latest inbound buyer message is awaiting a response
In-app action links in answers (for example low-stock/events/stock-groups)

6) Safety boundaries for unsupported factual lookups

For high-risk record-specific questions Eden cannot answer from deterministic facts yet, Eden now refuses the lookup before model fallback and links to the right ChannelWeave screen instead of guessing. This covers:

Specific order lookups and status checks
Unsupported record-specific lookups that are outside the allowlisted facts contracts above

Example questions

Use these as copy/paste starters in Eden.

Beginner orientation starters:

What should I do first?
Am I set up properly yet?
Do I need to connect a channel first, or add stock first?
Which channel should I connect first?
How do I connect my first channel?
How do I import or add my first stock items?
What does a healthy connection look like?
How do I know sync is working?
What should I ignore for now?
Where do I get help if I get stuck?
What plan am I on?
Am I being charged already?
Where do I manage billing or invoices?
Can I disconnect a channel cleanly?
What happens if I close the tab and do nothing today?
What is the Control Centre for?
What is the difference between Control Centre, Inbox, Sales, Inventory, Listings, and Eden?
Where do I find orders, messages, stock, listings, and settings?
Are these dashboard numbers live?
How fresh is my data?
Which warnings should I fix first?
What does this warning mean?
What is safe to click?
Which actions affect real business data?
Can I undo a mistake?
Will my team see what I am doing?
Will customers see anything yet?
Do I have the right permissions to do this?

Operational starters:

How did it go today?
What needs attention today?
How many stock items are there?
List 10 stock items with "black" in the name.
Which items are low stock?
How many low stock items do we have?
Which items are low stock in location "MAIN"?
Which SKUs are running low?
How many SKUs need reordering?
What is causing recent sync errors?
What broke on Shopify sync today?
Which channel jobs are failing today?
What is causing sync errors on Shopify in the last 24 hours?
Which custom insight rules are failing?
Which alerts need attention?
Why is custom rule "Warehouse low stock watch" failing?
What are the warn and fail thresholds for custom rule "Recent error events"?
How many stock groups do we have?
List 10 stock groups with "basic" in the name.
Which stock items are in the ABBA group?
Are there duplicate stock-group names?
What are the distinct stock-group names and codes?
Which stock group has the highest stock item count?
Which stock group has the lowest stock item count?
What is the average stock item count per stock group?
How many stock groups were created between 2026-01-01 and 2026-01-31?
How many stock groups were updated between 2026-01-01 and 2026-01-31?
Top 5 best-selling stock groups in the last 30 days.
Which stock groups sell the most?
Which stock groups make the most money?
Top earners among my stock groups last month?
Which ranges are flying out the door?
Top 5 stock groups by revenue in the last 90 days.
Why did stock group sales change in the last 30 days?
Count stock groups where name contains "denim".
Sum units sold for stock groups with "ath" in the name in the last 30 days.
Average revenue for stock groups with "tee" in the name excluding "oversized".
import stock, How do I import stock?, or first-time stock-upload prompts such as First time doing a stock upload — where do I start? → Eden should point to Inventory → Data exchange → Import stock items CSV, link to /inventory/stock/import, and mention reference_fact[Format], Reference fact source, and the Location + Bin requirement using location_code and bin_code for quantity imports.
How do I connect to eBay in ChannelWeave? → Eden should point to Control Centre → Manage eBay for Connect, Reconnect, or Disconnect actions, with links to /dashboard?manage=ebay and the eBay guide.
The Shopify connection is failing — what should I check?
Where's order #1234? → Eden should say specific order lookup is not available in Eden yet and link to /sales/orders.
How many of SKU ABC-123 do I have? → Eden should return exact stock-item quantities from the SKU lookup facts and link to Stock items.
Top 5 best-selling SKUs → Eden should return item-level sales ranking from sales-order-line facts, with a units-sold or revenue basis.
Is eBay connected? or When did Shopify last sync? → Eden should return channel connection status, attention state, and latest sync/probe facts.
What do I need to ship today? → Eden should return due-today dispatch queue orders and link to the Sales orders due-today filter.
Which messages need a reply? → Eden should return Inbox threads where the latest inbound message is waiting for an outbound response.
Can you put today's work in priority order for me? → Eden should return at most three read-only priorities from the daily operations facts and state that it has not changed any records.

Model-assisted capabilities (governed)

For broader questions not matched to deterministic handlers, Eden can still answer operational analysis prompts using governed facts context and clear uncertainty handling when data is insufficient.

Unsupported factual lookups listed in the safety-boundary section are handled before this model-assisted path, so Eden does not attempt to infer specific order status or other unsupported record-level facts from thin broad metrics.

Approved operating guidance includes starter coverage for:

No approved guidance fallback,
Stock import failure,
Missing, blank, no-SKU, or duplicate SKU handling,
Low-stock next steps,
Listing mapping and publish blockers,
Repeated channel sync failure triage.

Additional approved operational knowledge covers:

Order stock shortages, cancel-versus-hold decisions, partial dispatch, and ship-by risk,
Negative stock, manual adjustments, wrong-bin/location fixes, and suspicious Website orders,
Amazon, eBay, Shopify and Website, credential/scope, repeated queue, and channel-data disagreement guidance,
Buyer offers, order-problem messages, angry buyer responses, returns, refund mismatches, and address-change requests,
Manager escalations, approval gates, incident triage, audit trails, shift handovers, policy conflicts, privacy boundaries, and Eden knowledge acceptance tests.

Knowledge retrieval uses approved customer-specific guidance. Eden does not inject unrelated recent guidance when the user question has no positive knowledge match.

Examples:

Comparative trend questions across orders + stock groups,
Explanation/summary prompts outside deterministic templates,
Practical next-step framing based on available facts.

Important boundaries

Deterministic handlers have priority when intent is recognised.
The intent classifier runs only after the deterministic router misses. It can route natural seller phrasing such as “What’s waiting to be posted?” to the same account-scoped facts, but facts still come from ChannelWeave data.
Classifier precedence distinguishes sync failures from custom-rule alerts, specific-SKU quantities from catalogue counts, individual-item sales from stock-group sales, and dispatch work from sales metaphors.
Plan and billing-status answers use the signed-in account context passed by ChannelWeave. Users should still open Settings → Home for final plan, trial, renewal, invoice, card, and Stripe portal controls.
Channel-disconnect answers describe the connection contract: disconnecting removes the account’s channel connection and stored credentials, but it is not a stock, order, or listing delete action.
Common rewordings of supported questions — first-session orientation, setup confidence, safe exploration, low stock, reorder pressure, sync failures, sales ranking, and insight alerts — are expected to reach the same deterministic answers rather than a model-generated fallback.
The daily operations brief is deterministic and uses approved account data for sales, fulfilment, stock, channel/sync health, Inbox, warehouse movement, and custom insight state.
Operational planning is bounded to three deterministic priorities from the same daily fact pack. Clear plan wording bypasses page help; the classifier distinguishes broader plan requests from recaps. No model-authored action or mutation is executed.
Unsupported aggregate-query shapes return explicit “unsupported query shape” guidance.
Custom insight answers use safe rule, state, finding, and evidence summaries, not unrestricted data access.
Eden should state uncertainty when facts are missing rather than inventing.
Capability claims should be treated as contractual only when covered by ChannelWeave’s governed capability checks.