Elqori capabilities

Full capability list for Elqori.

Last updated: September 08, 2026

This page answers the practical question: what can Elqori help me do? The plus-menu starters are examples, not the complete capability list.

How to use Elqori

Choose the Elqori Orbit icon beside a page title for help grounded in that page and your current account state.
Open full-page Elqori when you need more room or want to continue a conversation.
Use the suggested questions as starting points, or ask the same question in your own words.
Delete saved conversations from the conversation list when they are no longer useful.

Elqori is local-first. Broader replies run through ChannelWeave’s controlled local model environment rather than a hosted model API. Exact operational answers use recorded ChannelWeave data; broader explanations use that data and approved guidance. When the required information is unavailable, Elqori should say so rather than guess.

Guided actions and drafting

Elqori appears inside selected workflows as well as in chat:

On Import stock, Elqori can explain the validated file, its destination, Reference fact choices, and the first errors or warnings. After a completed import, Draft missing descriptions with Elqori creates a separate review queue and never overwrites an existing Stock description.
On Stock item, Elqori can explain catalogue-readiness issues and guide the next step. Any proposed Stock change requires an explicit Apply action.
In Inbox → Messages, Ask Elqori can draft a plain-text buyer reply for eligible eBay and Website conversations. The draft is placed in the composer; Elqori does not send it.
In Stock and listing-draft forms, Draft with Elqori prepares concise copy from the approved buyer-visible facts. It does not add unsupported claims about condition, rarity, availability, fulfilment or packaging.
Add reference facts shows retrieved product facts for approval before they are used. Elqori receives only the facts you approve and does not silently fill required titles.

Facts-first capabilities

1) Profile and orientation

Greeting responses (hello, hi)
Thanks acknowledgements (thanks, thank you Elqori)
Today, yesterday, and tomorrow date questions in the browser's validated time zone
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, Elqori, channels, connections, listings, orders, and stock items

Elqori’s tone standard is warm precision: corporate-grade, calm, human, and concise. Elqori should understand casual chat without mirroring nicknames, gendered labels, flirtation, or personas, and does not volunteer gendered identity in customer-facing answers. Elqori 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 Elqori 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 Elqori may adapt the salutation, for example “Hey Elqori” 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 Elqori”. 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's first name, last name, and account name. Elqori 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 treat “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 Elqori and linked docs do not unblock the next step, users can open Ask the ChannelWeave team from Elqori surfaces to create a lightweight in-app support request.

2) Operational guidance

Concepts: stock groups, stock
How-to guidance: Channels, shipping, Stock, listings, orders, Warehouse, sync health, rules and automation, and Elqori
Troubleshooting: common issues, channel connection issues, listings-import issues, orders-import issues

3) eBay listing setup suggestions

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 totals, averages, minimums and maximums with optional filters
Stock-group sales change drivers:
- Paired-period comparison
- Top stock-group deltas
Allowlisted Stock Reference-fact breakdowns for Brand, Catalogue number, Colour, Format, Label, Manufacturer, Material, Media Condition, Released, Size and Sleeve Condition, with optional exact values and source scope
Stock quantities or period sales by those Reference facts, including coverage, currency-separated revenue and qualified gross margin before fees
Confirmed Discogs release classifications:
- Stock-item, on-hand and available quantities by exact genre or style
- Units, revenue and orders by exact genre or style for a requested period
- Explicit enrichment coverage, including releases not yet classified
- Revenue separated by transaction currency; gross margin before Channel fees only when sales currency matches Inventory valuation currency and every included line has recorded COGS

5) Operational risk checks

Daily operations brief for prompts such as How did it go today?
Read-only operational plans for natural requests such as Put today's work in priority order, using at most three steps from current account data
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 record-specific questions Elqori cannot answer reliably yet, Elqori links to the right ChannelWeave screen instead of guessing. This covers:

Specific order lookups and status checks
Other record-specific lookups not listed as supported above

Example questions

Use these as copy/paste starters in Elqori.

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 Elqori?
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? → Elqori should point to Inventory → Data exchange → Import stock items CSV and explain the Reference fact source and Location + Bin requirements.
How do I connect to eBay in ChannelWeave? → Elqori 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? → Elqori should say specific order lookup is not available in Elqori yet and link to /sales/orders.
How many of SKU ABC-123 do I have? → Elqori should return exact stock-item quantities from the SKU lookup facts and link to Stock catalogue.
Top 5 best-selling SKUs → Elqori should return item-level sales ranking with a units-sold or revenue basis.
Is eBay connected? or When did Shopify last sync? → Elqori should return channel connection status, attention state, and latest sync/probe facts.
What do I need to ship today? → Elqori should return due-today dispatch queue orders and link to the Sales orders due-today filter.
Which messages need a reply? → Elqori 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? → Elqori should return at most three read-only priorities from current account data and state that it has not changed any records.
How many Stock items have Discogs genre "Jazz"? → Elqori should use only confirmed Discogs classifications and report enrichment coverage alongside Stock-item, on-hand and available quantities.
How is Discogs style "Ambient" performing this month? → Elqori should keep sales totals separated by transaction currency and qualify gross margin against COGS coverage and Inventory valuation currency.
How many Stock items have brand "Acme"? → Elqori should report matching Stock, on-hand and available quantities plus Brand Reference-fact coverage.
How is Discogs label "Blue Note" performing this month? → Elqori should use Discogs-sourced Label facts, keep revenue separated by transaction currency and state when gross margin cannot be calculated safely.

Model-assisted capabilities (governed)

For broader questions, Elqori can explain operational information using recorded ChannelWeave data and clearly state when the available information is insufficient.

For unsupported factual lookups, Elqori does not infer a specific order status or other record-level detail from broad summary information.

Approved operating guidance includes starter coverage for:

A clear response when no approved guidance is available,
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, and privacy boundaries.

Elqori uses approved customer-specific guidance only when it is relevant to the question.

Examples:

Comparative trend questions across orders + stock groups,
Explanation and summary prompts outside exact facts-first questions,
Practical next-step framing based on available facts.

Important boundaries

Exact operational answers come from recorded ChannelWeave data.
Elqori does not automatically reconcile ChannelWeave quantities against another system's stock records. When switching systems, compare the figures manually; import-validation help does not establish cross-system agreement.
Natural seller phrasing such as “What’s waiting to be posted?” can reach the same facts as the more formal example questions above.
Plan and billing-status answers use the signed-in account. 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.
Daily operations briefs use account data for sales, fulfilment, Stock, Channel health, Inbox, Warehouse movement, and Custom insight state.
Operational plans contain at most three read-only priorities. Elqori does not execute the plan or change records.
Unsupported summary questions receive a clear limitation instead of a guess.
Custom insight answers use the saved rule, current state, findings and supporting evidence rather than unrestricted data access.
Elqori should state uncertainty when facts are missing rather than inventing.