Use Mink AI in your dashboard

Open the dashboard assistant

1. Sign in to the correct store dashboard.
2. Select the Mink AI button in the top bar, or use Ask anything on Home.
3. Enter a store or product question and send it.
4. Watch the activity label while Mink AI checks an allowed StoreMink tool.

Select Expand to open Mink AI across the full browser window, covering the dashboard topbar, left navigation and page content. On a phone, both the Home prompt and the topbar Mink button open a full-screen conversation: recent conversations start closed behind the sidebar button, the dashboard underneath cannot scroll, and typing keeps the composer at its full width without zooming the page. On larger screens, select Collapse to return to the drawer. Drag the left edge of the desktop drawer to make it wider or narrower; StoreMink remembers that width in this browser. New conversation starts a separate topic.

Continue recent conversations

Mink AI keeps the 10 most recent conversations for each admin in each store. The purple robot mark in the dashboard header opens Mink AI. Inside Mink AI, select the conversation-sidebar button to show or hide recent threads. The sidebar stays beside the chat in the expanded view and slides over the narrow drawer. Select a title to continue it.

To remove a thread, select its Delete conversation button and confirm Delete. This permanently removes its messages, run records, tool records and token record. Mink AI opens the next recent thread when the active thread is deleted. The newest remaining conversation is restored after a dashboard refresh. Starting a new conversation keeps the newest ten visible. Ordinary overflow is removed automatically; an older conversation tied to a retained publication or completed action stays safely outside the recent list instead of blocking the new conversation.

Mink AI answers display supported emphasis and inline code as formatting, so formatting markers such as double asterisks are not shown as part of the answer.

The message box grows as a prompt wraps onto more lines, up to a scrollable maximum. Press Enter to send or Shift+Enter to add a new line.

Questions Mink can answer

• What plan is this store using?
• How many products are published or in draft?
• Find a product by its name or SKU.
• What were net sales today, yesterday, over the last 7 or 30 days, month to date, or year to date?
• Which tracked products or variants are low or out of stock?
• Which offers are running now, scheduled, disabled or unable to run?

Sales answers state the store timezone, date range, currency, location scope and when the data was read. Net sales use the same recognised-order and completed-refund rules as dashboard Analytics. Low-stock answers use each item threshold, falling back to the store default, and link back to Inventory or the product.

Cards, filters and dashboard context

Grounded answers can include metric, order, product, inventory and Help Centre cards. Filter chips show the period, store timezone, accessible location scope, sales channel and status used. Open a card link to inspect the supporting dashboard screen or published guide.

For a location-specific question, use the location name shown under Locations. You may include its displayed type, for example Delhi warehouse for a Warehouse named Delhi. StoreMink resolves that phrase only when it identifies one location the signed-in admin may access. A wrong type, duplicate name or inaccessible location is refused; Mink AI does not replace a failed named-location request with all-store results.

Mink AI receives the current dashboard path. When a product editor or order drawer is open, it can use that selected record only after StoreMink revalidates the record against the signed-in store and permissions. A browser-supplied ID never grants access.

Orders and customer privacy

Orders → View is required for order questions. Order results are limited to compact operational fields. Staff without Customers → View see customer details hidden; permitted staff receive only a minimized first-name and last-initial label. Email addresses, phone numbers, addresses, notes and payment credentials are not sent to the dashboard agent.

Help Centre guidance

For setup, navigation and troubleshooting questions, Mink AI searches published StoreMink Help Centre articles using keyword and semantic retrieval. Source cards link to the published guides. Mink AI must say when those guides do not confirm an answer.

Read catalogue and stock health

Ask Mink for published, unpublished, draft and archived products to receive product-level counts plus a bounded list of products and variants with visible status badges. Draft and archived products are also unpublished, so Unpublished is a total while Draft and Archived explain that total.

Low-stock and out-of-stock counts are sellable-SKU counts: a simple product without variants counts as one SKU, while every variant is evaluated separately. Mink uses the same per-SKU threshold and store-default fallback as the Inventory workspace. It shows the stock quantity, low-stock threshold and an In stock, Low stock, Out of stock or Not tracked badge when the signed-in admin has Inventory → View.

When a stock question does not say whether it means combined stock, each location or one exact location, Mink does not silently assume an all-location total. If the admin can access more than one active location, it asks one clarification and offers buttons for Compare locations, Combined stock and up to four exact accessible locations. Selecting a button sends the visible follow-up request. If only one active location is accessible, Mink uses it automatically. Publication-only questions do not require an inventory choice.

Compare locations evaluates every tracked sellable SKU independently at each accessible shelf and shows low-stock and out-of-stock counts side by side. A missing inventory-level row counts as zero at that shelf, just as it does in the Inventory workspace. The comparison is bounded to the first 20 accessible locations; select List this location's SKUs or name another exact dashboard location for its tagged product and variant list. Combined stock uses the trusted all-accessible-location aggregate and never represents that aggregate as one shop or warehouse. Publication counts always describe the current store.

Mink formats supported headings, lists, tables, emphasis, code and StoreMink links for readability. Model text is never treated as raw HTML, and arbitrary external links are not made clickable.

Permissions and store isolation

Mink AI uses the store from the current dashboard host, the location assignments and the permissions of the signed-in admin. It does not accept a store ID, location ID, role or permission from a message. Products → View is required for catalogue tools, Analytics → View for sales, Inventory → View for low-stock lists, and Offers → View for offer status. Offer answers distinguish an enabled offer from one that can run now by checking its dates, redemption and budget limits, delivery method, and the store-wide automatic-offer switch. For an item offer, Mink reports the named products, variants and categories under Applies to separately from the order trigger, so "on any order" does not mean "all products". A running offer may still depend on a particular shopper's basket or other saved conditions. Asking for a hidden tool by name does not bypass those checks.

Current limits

Mink answers questions on its own. Everything that changes your store is prepared as a private proposal that you review and approve yourself, and the sections below describe each one. Mink never cancels an order, refunds or captures money, changes a payment state, creates or edits a shipment, transfers stock between locations, messages a customer of its own accord, changes who is in a customer group, publishes a product, edits your header or footer, or touches StoreMink's own code. It tells you when something is outside what it can do instead of reporting an action it did not complete.

Select Stop to cancel the request in this browser. If a temporary error appears, select Retry. StoreMink keeps up to 10 recent conversations per admin and store, including messages, run status, tool names and token counts, for continuity, reliability and cost monitoring. Asking questions does not spend AI credits. Asking Mink to draft or propose something does, at the rate shown before you confirm it.

Conversation context and feedback

The dashboard keeps the 10 most recent conversations. For longer follow-ups, StoreMink keeps the newest turns verbatim and compacts older turns into a bounded extractive summary. This summary contains conversation text only and never model reasoning.

Use the thumbs-up button when an answer helped. Use thumbs down to report an incorrect answer, missing context, privacy concern, slow response or another issue. Optional report details are bounded and common emails, phone numbers, credentials and identifiers are redacted before support storage; do not enter private customer data.

Beta usage records an estimated provider cost, a read-lookup or read-analysis cohort and shadow credits. Shadow credits help StoreMink set fair future weights and do not debit the store's AI-credit balance.

Private content drafts

Stores separately enrolled in the drafting beta can ask Mink AI for a product description, product SEO, blog post, coupon email or reusable customer-message template. The signed-in admin must have Manage permission for the related Products, Blogs, Marketing or Customers area. StoreMink also applies the store's saved brand voice as style guidance; it never grants authority or overrides safety rules.

Mink AI first shows a proposal card with the current text, proposed text, destination and expected credit weight. Product SEO costs 1 AI credit; product descriptions, coupon emails and customer messages cost 2; blog drafts cost 5. StoreMink consumes the monthly plan allowance first and then purchased or granted credits. The composer estimate is a preview; the server calculates and charges the authoritative amount exactly once when it creates the proposal.

A proposal is private to the admin who requested it. Choose Save private draft to create version 1. Later saves create immutable versions, and rollback creates a new version from an earlier one so the audit history is preserved.

Saving and restoring versions affect only the private Mink draft. Mink AI still cannot publish a product or blog, change a product's price, stock or status, send an email or message, or contact a customer. A separately enabled product-text action can change only the product description or SEO fields shown in its exact approval preview.

Approved product-text actions

StoreMink support must enable product-description and product-SEO actions separately for the store. These are independent kill switches on top of the Mink beta and private-drafting gates. The signed-in admin must also have Products → Manage permission.

First save the private product description or product SEO proposal. Choose Review product change to see the exact current and replacement values. The preview expires after 10 minutes and is bound to that saved draft version, the linked product, its current content version and the signed-in admin. The browser cannot replace the approved text when executing it.

Choose Approve and apply only after checking every shown field. Product-description approval changes only the description. Product-SEO approval changes only the SEO title and SEO description. The action never changes price, inventory, variants, status, publication, images or any other product field. Published products may show approved text to shoppers after the storefront cache refreshes.

StoreMink executes the approved fields in one database transaction and records the before value, after value, actor, draft version, product version, action version and outcome in an append-only audit row. Retrying the same completed approval is idempotent and cannot apply it twice.

After a completed change, choose Review safe rollback to create another exact preview. Rollback is allowed only while the product still matches the completed action's content checkpoint. If the product or private draft changed after preview, StoreMink refuses the action without overwriting newer work; reload the latest product or draft and review again.

Creating products, coupons and customer groups

StoreMink support must enable each live-action tool separately. You must have the matching Manage permission, save the private proposal, review an exact preview, and then choose Approve. Previews expire after 10 minutes and are bound to your account, store, saved proposal version and current destination checkpoint. Retrying a completed approval cannot execute it twice.

New products: Mink can create only an unpublished draft product with inventory tracking off. The exact preview includes its name, URL slug, description, SEO text and prices. Mink cannot choose a category, add variants, images, stock, tax or shipping settings, feature the product, or publish it. Finish those settings in the normal product editor.

Coupons: Mink can create a new coupon or edit terms on an existing coupon only while it is disabled and hidden. It cannot activate the coupon, show it on the storefront, change its used count, add customer-group restrictions, send it to anyone or schedule a campaign. Enable and distribute the coupon later through the normal Marketing workflow.

Customer groups: Mink can create or update only the group name, description and colour. It cannot add or remove customers, change coupon audiences, export customer data or contact anyone. Membership remains a separate manual workflow.

Every approval and outcome records the actor, store, proposal version, exact before and after values, resource checkpoint, action version and outcome in the Mink action audit. If the proposal or destination changes after preview, StoreMink refuses the action rather than overwriting newer work.

Completed actions offer a safe rollback preview. Updates roll back only while the destination still matches Mink's last checkpoint. A newly created record can be removed only while it remains unchanged and unused: draft products must have no variants or order lines, coupons must be disabled, hidden, unused and unlinked, and customer groups must have no members or coupon links. Otherwise rollback is refused.

Proposal and approval reliability

A generated proposal appears as a private proposal card in the live answer and in the retained conversation after a refresh. The card contains the saved proposal and its Review controls; plain answer text is not a substitute for that card. If a proposal cannot be restored, retry from the original prompt before generating another one so you can verify whether credits were already charged.

StoreMink controls general Mink availability and private drafting separately. Removing the invitation-only rollout requirement does not enable drafting for every store: StoreMink support must still enable the store's drafting switch, and the signed-in admin still needs the matching Manage permission. Each live-action tool remains independently disabled until support enables it.

Approval checks use the exact database checkpoint captured by the preview. An unchanged destination can be approved normally, including coupons whose date fields use an equivalent display format. If another person or tab changes the destination after preview, Mink refuses the old approval and asks you to review a new one. The same checkpoint rule protects rollback from overwriting later manual work.

Adjust one SKU at one location

Mink can propose a stock adjustment only for one exact inventory-tracked product or variant SKU at one exact active location you can access. Ask with the visible SKU, either a signed quantity change or absolute target quantity, the location name and a reason. Mink first reads the current on-hand and reserved quantities, calculates any absolute target from that checkpoint, then creates a private proposal. It cannot use hidden IDs, adjust an untracked item, choose an inactive or inaccessible location, change multiple SKUs, transfer stock, change reservations or silently select a default location.

Save the proposal, select Review exact change, and verify the SKU, location, current on-hand quantity, signed change, resulting on-hand quantity, reason and audit note. The approval expires after 10 minutes. You need Inventory Manage permission, and StoreMink support must enable the single-SKU inventory action separately for your store.

Approval rechecks your account, store, permission, assigned location, SKU tracking state, saved proposal version and exact stock checkpoint. If stock changed in another tab, through POS, an order, import or another admin after the preview, Mink refuses the stale approval. Stock can never be reduced below zero or below its reserved units, a single change is limited to 1,000,000 units, retries cannot apply the action twice, and a successful adjustment writes the inventory level and stock-movement ledger in one database transaction.

Inventory corrections do not offer automatic rollback because physical stock may move after approval. To correct a completed adjustment, review the current stock and create a new explicit proposal with the inverse quantity. The single-SKU action does not silently become a bulk action. Use the separately enabled bulk workflow for multiple exact SKU/location lines. Transfers, order-status changes, publishing, campaigns and price updates remain unavailable.

Adjust multiple inventory lines

Mink can prepare a private bulk proposal for between 1 and 20 exact inventory-tracked SKU and active-location pairs. It reads every line in one bounded batch, returns the current on-hand, reserved and available quantities, and reports an error against each missing, duplicate, ambiguous, untracked or inaccessible line. Mink does not create or charge a proposal until every line has a valid checkpoint. It cannot use hidden IDs, select a default location, transfer stock or change reservations.

Each line needs a signed whole-number quantity change or an absolute target calculated from the returned checkpoint, plus a reason and an audit note when the reason is other. Save the private proposal and select Review exact change to compare every current and resulting quantity. You need Inventory Manage permission, and StoreMink support must enable Bulk inventory adjustments separately from the single-SKU action.

The exact approval expires after 5 minutes. Approval rechecks the current admin, store, permission, assigned active locations, tracking state, proposal version and every inventory timestamp, on-hand and reserved value. A duplicate SKU/location pair, invalid quantity, stock below zero or reserved units, or any stale line blocks the entire batch. Execution is atomic: either all lines and their stock-movement ledger entries commit once, or the database rolls the whole batch back. Retries cannot duplicate movements, events, alerts or stock changes.

Completed physical-stock batches do not offer automatic rollback. Review current quantities and create a new proposal for any correction. Bulk actions are capped at 20 lines to bound database work and review risk. Stock transfers, order cancellation, refunds, payment changes, pickup/POS lifecycle changes, publishing, campaigns and bulk price changes remain unavailable.

Advance one delivery order

Mink can prepare a private proposal for one exact visible online delivery-order reference to move one forward step: pending → processing, processing → shipped or shipped → delivered. It first reads a permission- and location-scoped order checkpoint. The checkpoint includes the current order, payment, cancellation, fulfilment, assigned-location and latest carrier-shipment state. Mink cannot use an internal order ID, skip a step, move backwards or propose a different status.

Save the private proposal and select Review exact change. You need Orders Manage permission, drafting access and the separately enabled Delivery order-status transitions switch. The preview shows the current and proposed status plus material payment, channel, fulfilment, location and shipment context. The exact approval expires after 5 minutes.

Approval rechecks the signed-in admin, store, assigned locations, permission, operator switch, proposal version, order timestamp and every material checkpoint field inside one database transaction. A payment, cancellation, location, shipment or status change makes the approval conflict. Retries are idempotent: the status, approval and append-only audit commit once, and only a newly completed execution emits the normal order-status event.

This action is deliberately narrow. POS sales use the register lifecycle; pickup orders use the collection workflow. Mink does not cancel or complete orders, change payment state, capture or refund money, create or modify a shipment, transfer stock, send a message or email, or perform a bulk transition. Non-COD delivery orders must already be paid. Pending or approved cancellation states and any refund activity block advancement; a previously declined cancellation is evaluated under the normal order rules. When a carrier shipment exists, Mink will not mark it shipped before pickup/transit evidence or delivered before carrier-confirmed delivery, and shipment exception/return states must be resolved in the shipment workflow.

Completed order-status actions do not offer automatic rollback. If a manual correction is needed, open the order and use the established Orders and shipment workflows; do not create a reverse Mink transition.

Publish or schedule one blog

Mink can prepare a private Markdown blog proposal with a title, excerpt, body and optional SEO title and description. Save the proposal, choose Publish after approval or Schedule for later, then select Review exact change. You need Blogs Manage permission, drafting access and the separately enabled Blog publication and scheduling switch.

The preview shows the complete saved content, publication mode and exact UTC instant. It expires after 5 minutes and cannot accept a title, body, tenant ID or blog ID from the browser. Approval rechecks the signed-in store and admin, permission, switches, saved version and cryptographic payload hash inside one transaction. It creates one new blog only; retries return the original result without a second post, audit or discovery notification.

Publish after approval makes the sanitized post live immediately. Schedule for later accepts a time from 5 minutes to 90 days ahead and first creates a private draft. An authenticated, bounded worker checks due jobs once per minute. Disabling Mink, drafting or the publication switch pauses scheduled jobs. Editing or publishing the blog through another workflow before its due time produces a conflict instead of overwriting that work. Deleting the private blog also removes its pending publication job, so the worker cannot recreate it.

Raw HTML is escaped and sanitized. The blog workflow supports a small Markdown subset and deliberately does not activate Markdown links, attach media, assign categories or tags, feature a post, publish a product/page/storefront version, send a campaign, contact a customer or publish every draft in bulk. Scheduled jobs have no automatic rollback; use the Blogs workspace to unpublish or edit a post after publication.

Send or schedule one coupon-email campaign

Mink can prepare a private coupon-email proposal linked to an existing coupon. Save the proposal, choose All customers or one exact customer group, choose immediate delivery or a time from 5 minutes to 30 days ahead, then select Review exact change. You need Marketing Manage permission, Pro email-campaign access, drafting access, configured email delivery and the separately enabled Coupon email campaigns switch.

The server—not prompt text or browser fields—loads the signed-in store, saved subject and body, active coupon, sender identity and current audience. StoreMink caps the source audience at 10,000 customer rows. It excludes missing or invalid email addresses, duplicate normalized addresses and globally suppressed addresses before producing a SHA-256-bound recipient snapshot. The preview shows the audience label, eligible and excluded counts, timing, sender, coupon terms, complete copy and a branded sample rendered for the literal name “Customer”; it does not expose a real recipient address or name.

The preview expires after 5 minutes. Final confirmation rechecks permission, plan, switches, proposal version, coupon version, sender and the exact audience hash inside one transaction. Any drift produces a conflict instead of sending to a different audience. One confirmation creates one campaign, the exact recipient rows, one approval result and one audit record atomically; retries return the original result and never duplicate a campaign. Gemini cannot call the options, preview or execution endpoints.

Immediate delivery is queued only after final confirmation. Scheduled delivery reuses StoreMink's authenticated email worker, which promotes due jobs before claiming recipients and never claims a future campaign. The approved sender and brand are snapshotted, so later branding edits do not silently change scheduled email. Suppression is checked again at delivery. Mink does not accept arbitrary recipient IDs, multiple groups, attachments, direct customer messages or a model-triggered send. Queuing is a final send instruction and has no automatic cancellation or rollback; use a small internal test group before a broad campaign.

Update prices for up to 20 exact SKUs

Mink can prepare one private bulk-price proposal for 1 to 20 exact sellable SKUs. Products with variants require each exact variant SKU; a parent product SKU is rejected. Save the proposal and select Review exact change. You need Products Manage permission, drafting access and the separately enabled Bulk price updates switch.

Every line contains the complete INR price set: MRP, selling price and either a special price or an explicit instruction to clear it. Special prices are available only for variant SKUs; a product without variants must keep that field cleared, and Mink rejects a value instead of silently ignoring it. Prices must use at most two decimal places, remain within StoreMink's supported range and satisfy MRP ≥ selling price ≥ special price > 0. The server rejects duplicate, missing, ambiguous, unchanged or invalid SKU lines.

The preview expires after 5 minutes and shows every before-and-after price, effective-price change and an impact summary based on one unit of each selected SKU. This summary is not a sales or revenue forecast. Existing orders retain their saved prices; future storefront, checkout and POS carts use the live prices after confirmation.

Final confirmation rechecks the signed-in store, admin, permission, switch, saved draft version, product and variant identity, publication status, version and every current price. The entire set applies atomically: any stale or invalid line changes nothing. Retries return the original result and never apply twice. Gemini cannot call the preview or execution endpoint, choose database IDs or bypass the 20-line limit.

Bulk price updates do not have automatic rollback because shoppers may act on a live price. To correct a confirmed update, review a fresh proposal or edit the product manually. Test a small unpublished set first when changing unfamiliar prices.

Create a durable weekly trading report

Ask Mink to create, prepare, run or generate my weekly trading report. You need Analytics View permission. Mink queues a background workflow for the last 7 days in the store timezone, compares it with the preceding equal period, and shows net sales, orders, average order value, units sold, leading products and sales channels.

The report snapshots the exact active locations accessible to you when it is queued and re-checks Analytics access, account status, beta access and restricted location assignments before each step. Removed access takes effect before the next read, while a later location cannot silently enter an existing run. Online or unassigned orders are included only when your dashboard aggregate would include them. Headline net sales include completed refunds; top-product merchandise line totals are labelled separately.

The progress card survives a refresh, and a report is never counted twice or left half-finished if StoreMink restarts while it runs. The report period is anchored to the moment you asked, so a retry after midnight does not silently change its dates. Asking for this report does not set up a recurring schedule, and it never changes products, inventory, prices, orders, customers, content or settings.

Select Stop to request cancellation. A queued report stops immediately; a running report stops safely after its current bounded read. Cancelled workflows cannot resume. Workflows waiting at a future human-approval checkpoint can resume only through their authenticated dashboard control and consume no model tokens while waiting.

When the report completes, StoreMink adds an in-dashboard notification. Completion delivery is reconciled and idempotent, so overlapping worker calls do not create duplicate alerts. The report card keeps its complete progress history and data-as-of time so support can reconstruct queue claims, retries, steps, cancellation and completion without storing model reasoning.

Investigate a revenue decline

Ask Mink to investigate, diagnose or explain a revenue decline over the last 7, 30 or 90 days. You need Analytics View permission. Mink compares that period with the preceding equal period in the store timezone and checks recognized net sales, order count, average order value, units sold, sales channels, accessible locations and the bounded set of leading product movements.

You may name one exact accessible dashboard location, such as Shop or Delhi warehouse. Otherwise the workflow captures your exact accessible active-location scope and labels whether online or unassigned orders are included. Access, suspension, beta eligibility and location assignments are checked again before every background read. The result reports evidence and correlations, not invented causes: advertising spend, external traffic and competitor activity are unavailable unless StoreMink records them.

Use a normal sales question for a quick total. The durable investigation starts only after an explicit investigate/diagnose request, survives restarts and can be stopped safely at any time.

Prepare a private product launch package

Ask Mink to prepare a launch-readiness package for one exact existing product or variant SKU. You need both Products View and Inventory View. The SKU is resolved inside the current store; product names are never expanded implicitly. Mink inspects at most 20 sellable SKUs and checks publication state, parent and relevant variant media, saved description and SEO coverage, valid MRP/selling/special-price hierarchy, stock and low-stock thresholds across the captured accessible active locations, and required shipping measurements. Missing stock rows count as zero at that location, and Mink flags a location-level gap even when combined stock is positive elsewhere.

The completed private card separates blockers, items needing attention and ready checks. It includes an ordered launch checklist and clearly labelled starter copy grounded only in the saved store, product, variant and category names. The package does not generate an image, publish or edit a product, change prices or inventory, create or send a campaign, select recipients, deploy code or contact a customer. Any later change must use the relevant saved proposal and human-approval flow.

Both templates use the same service-only workflow ledger, short leases, idempotent checkpoints, bounded retries, safe cancellation, owner-and-store status endpoint and duplicate-safe completion notification as the weekly report. A location added later cannot enter an already queued run; removed permission or location access takes effect before the next read.

Find slow inventory and prepare a promotion

Ask Mink to identify slow-moving inventory and prepare a private promotion recommendation over a complete 30-day or 90-day lookback. You need Analytics View, Products View, Inventory View and Offers Manage, and Mink drafting must be enabled for the store. You may name one exact accessible dashboard location, such as Shop or Delhi warehouse; otherwise Mink checks each accessible active physical location separately.

A candidate must be a published, inventory-tracked SKU with current positive on-hand stock whose product predates the complete lookback. Mink compares the current shelf with recognized order-item sales attributed to that same physical location. No sales in the window, or enough stock for at least two equal lookback periods at the observed rate, is marked for review. Zero-stock and untracked items are not called slow inventory. Shop stock cannot hide Delhi stock, and online or unassigned orders are not invented as physical-location demand. Current stock may have changed during the window, so the card never claims it was present for the whole period.

The durable card shows at most 20 highest-priority SKU-location shelves, their on-hand stock, units sold, estimated days of cover and sell-through, plus a maximum-five-SKU promotion concept. A conservative percentage may appear only when saved cost data supports a five-point gross-margin buffer and the store discount ceiling. Missing or insufficient margin data withholds the percentage instead of guessing.

This is a private recommendation only. Mink does not create or activate an offer, change a price or inventory quantity, choose recipients, or contact customers. The analysed location is evidence scope, not an offer-eligibility boundary. The merchant must separately verify exact product or variant scope plus channel and audience rules in Offers, choose a total budget, save any offer disabled for review, and approve activation in a separate human step. Sales history is not a forecast, and seasonality, incoming stock, traffic and advertising spend are not included.

The workflow captures exact active location IDs at queue time and rechecks drafting, store access, suspension, Analytics, Products, Inventory, Offers and location authority before background reads. Removed access cancels or narrows the next step; a location added later never enters the run. Work is bounded, restart-safe, cancellable and completed without additional Gemini calls or tokens.

Review delayed pickups and prepare communication guidance

Ask Mink to review delayed, overdue, unprepared, uncollected or at-risk pickup orders and prepare private communication guidance. You need Orders Manage, and Mink drafting must be enabled for the store. Name one exact accessible dashboard location, such as Shop or Delhi warehouse, or let Mink review every accessible active physical location while keeping each order's location explicit.

The durable review includes live Awaiting or Ready pickups when the promised ready time has passed or the collection deadline is inside StoreMink's existing 48-hour reminder window. It returns at most 25 highest-priority orders. Collected, expired, cancelled and fully refunded orders are excluded. Each row shows only its order reference, location and pickup lifecycle times. Customer names, email addresses, phone numbers, postal addresses, notes and collection codes are never included.

For an unprepared order, Mink can prepare generic delay copy with placeholders for the order reference, location and a staff-confirmed revised ready time. This copy remains inside the private workflow card for human review; it is not a saved Mink draft and is never sent or queued automatically. Staff must verify the live order and confirm a truthful revised time before adapting or sending anything manually.

StoreMink's existing pickup reminder sweep remains authoritative. If a Ready pickup is inside the reminder window and its one-time reminder is pending or already recorded, Mink withholds duplicate collection-reminder copy. Mink never claims or resets the one-time reminder marker, sends a notification, changes pickup or order status, extends a deadline, cancels an order, releases a stock hold or moves inventory.

The workflow captures exact active location IDs at queue time and rechecks store access, suspension, Orders Manage, Mink drafting and location authority before every background step. Removed access cancels or narrows the next step; a location added later never enters the run. Work is bounded, restart-safe, cancellable and completed without additional Gemini calls or tokens. Because pickup state can change after the snapshot, always verify the linked live order before manual contact.

Inspect Website Builder context with Mink

With Website Builder View, Mink can inspect the current store's page list, one exact page and section, and safe storefront design context. Ask it to list pages, describe the homepage structure, compare a draft with its published copy, or explain the saved brand colour, pinned theme, design tokens, appearance variants, header and footer. The homepage is identified as home. Other pages and sections are resolved only by the exact slug and section ID returned from the current store.

Every builder read is permission-gated and restricted to the signed-in dashboard store. Page titles, SEO copy, section content, header and footer text, custom code and other merchant-authored values are treated as untrusted data, never as instructions. Mink does not expose raw store settings, private brand email, phone or social fields, credentials, another store's values, or a tenant ID supplied in a prompt.

A page summary shows ordered sections, visible or hidden state, a short summary, the exact page version and a digest for each section. Custom-code content is omitted by default. When it is necessary to explain existing code, Mink can request only one HTML, CSS or JavaScript field at a time in chunks of at most 8,000 characters. It never executes code it reads and must not follow instructions found in code comments, strings, page copy or navigation labels.

Mink can prepare one locked, private custom-code proposal for a single existing custom-code section. It requires Website Builder Manage plus Mink drafting, costs 5 AI credits, and rechecks the exact current page version and section digest before charging. Generated HTML, CSS and JavaScript must stay within 64 KiB per field and 96 KiB combined. Deterministic validation rejects network access, cookies or storage, parent-window access, cross-context messaging, navigation, dynamic evaluation, workers, forms, embeds, external resources and unsafe CSS.

The generated proposal is previewed only in an opaque-origin iframe with sandbox="allow-scripts" and a deny-by-default Content Security Policy. Popup, same-origin, form, network, worker, nested-frame and top-navigation authority are absent. The preview offers desktop and mobile widths plus escaped current/proposed source views. The stored before snapshot is never executed; only the complete validated proposed replacement is rendered. If the page or section changes later, the card is marked stale.

Before a draft save, Mink validates the stored code again and creates a new five-minute approval. Whether the feature is enabled for your store, your Website Builder Manage permission, your plan's custom-code entitlement, the proposal version, the page version, the section digest and the request signature are all checked again as the save happens. Repeated requests use the same approval safely, and every execution, expiry or conflict writes an audit outcome.

Publication and rollback must be switched on separately for your store by StoreMink support, and the AI model is never able to run either of them. The signed-in human initiates every check, review and approval. The server revalidates the tenant, proposal owner, Website Builder Manage permission, custom-code entitlement, source approval, browser evidence, full page snapshots and optimistic page version inside the transaction. Repeating a request cannot publish twice, and every execution, conflict and expiry is recorded in an audit trail that is only ever added to.

An approved save reaches the private Website Builder draft only. For an existing custom-code section, choose Review Builder draft save, inspect the complete current and proposed source, then choose Approve and save Builder draft within five minutes. The approval is tied to the current store, signed-in admin, immutable proposal, exact page version and exact section digest. If any of them changes, nothing is saved and you must generate a fresh proposal. StoreMink support must separately enable Website Builder draft code saves for the store.

A code draft save replaces only the reviewed custom-code section. A layout draft save replaces the page's whole section list, so any section you leave out of the proposal is removed — check the Removed from the page list on the card before you approve. A design draft save replaces your colours, typefaces and corner roundness on every page at once; anything the proposal leaves unset goes back to inheriting your theme, and the card draws the theme's own colour so you can see what that will look like. None of the three changes your header or footer, and none of them publishes anything. Publishing is a separate, separately approved step: choose Run publication checks to execute the proposed section in opaque-origin 1,280 px desktop and 390 px mobile frames. Publication remains unavailable unless current-browser runtime, horizontal-overflow, Content Security Policy and bounded accessibility checks all pass. Then choose Review storefront publication and Approve and publish storefront within five minutes. StoreMink support must separately enable Checked storefront publication and rollback for the store.

The publication approval is bound to the completed draft save, exact private Builder draft, exact current live snapshot, page version and complete section digests. It copies that checked draft snapshot to the live page; it cannot add sections, edit header/footer, access StoreMink source code or shell, commit code or deploy production. A completed Mink publication exposes Review exact rollback. Rollback requires another five-minute approval, restores only the exact prior published snapshot and fails closed if the live page changed after publication.

Draft troubleshooting

If drafting tools are unavailable, ask a store owner to check your Manage permission and ask StoreMink support whether the separate drafting beta is enabled. If the proposal cannot be created, check the plan's remaining monthly AI allowance or AI-credit balance under Plans & Billing. If the enclosing Mink run fails or is cancelled after creating a proposal, StoreMink discards the unseen proposal and restores its exact plan and purchased-credit amounts. A version conflict means the draft changed in another tab; reload the card before saving again.

Temporary failures and monitoring

Mink AI retries a transient model failure at most once. Each request also has a hard time limit; if it is reached, Mink AI stops and shows a safe retry message. These tools are read only, so a retry cannot duplicate a business change.

StoreMink operators can inspect redacted run status, latency, retry count, tool names, token usage and estimated model cost for reliability and cost monitoring. The inspector never displays prompts, answers, tool arguments, tool results or model reasoning. Interrupted usage is labelled partial or unavailable instead of being shown as zero cost. The alpha still does not debit AI credits.

Protect private information

Do not enter passwords, one-time codes, payment credentials, card details, API secrets or unnecessary private customer information. Mink AI does not need them for the supported read-only questions.

Use Mink while editing your website

Open Website Builder and click the purple Mink AI icon in the shared top header. The conversation opens over the right side of the editor, including on wide desktop screens. Resize the panel, expand it to full screen, restore it or close it without leaving Builder. Opening or closing chat does not save or publish your page.

Ask naturally, for example: "What needs restocking?", "What pages do I have?" or "Make the first custom-code section on my homepage look better on phones." You do not need to name internal tools or security rules. Mink may ask a short question when a product, location or requested change is unclear.

Builder tools read saved page data, not unsaved changes in your editor. Mink can propose a page's whole section list — adding, removing, reordering and reconfiguring blocks such as a hero, gallery, testimonials or featured products — for 3 AI credits; it can propose your storefront's design — its colours, its two typefaces and its corner roundness — for 2; and it can separately propose replacement code for one existing custom-code section for 5. Custom code is the boundary between them: a layout proposal must carry every existing custom-code section through unchanged, and cannot add, edit or delete one. A design proposal changes no page content at all, and it is refused outright if the colours would leave your body text hard to read, so you are told which pairs failed instead of being shown an approve button over an unreadable shop. Mink never makes up an address for a picture: a layout proposal may use only pictures from your Media library, pictures already on the page it is changing, an image you attached for that page, or a new picture Mink has just created for you. A file selected with the plus button appears as a removable preview card in your message. If your message clearly asks to use an attached image in a named storefront destination — for example a homepage carousel, hero, banner or gallery — or you hand over the product image for the storefront task already being discussed, Send saves your image under Media and Mink prepares the private page change in the same response. The attached file is used directly, so you do not need to upload or describe it again. For a product promotion, Mink uses the image you attached or searches the named product in your catalogue and uses its authentic product photo. It keeps that photo intact and puts offer wording in the editable carousel text. The result shows one Apply to Website Builder draft button in chat. It performs the safety check and saves the private draft in one click; publishing remains a separate step in Website Builder. For other image or document questions, open the preview card and review the extracted text before adding it to your message; that review does not save the original file. If you explicitly ask Mink to create a new decorative picture, say what it is for and describe the scene. Mink chooses a suitable shape, makes one picture, saves it under Media and shows it to you with the wording screen readers will read out. Image generation costs AI credits; for a page redesign that does not need a new picture, Mink checks the images you already own first. A created picture is decoration, not a photograph of your goods, and Mink cannot set one as a product image. Every created picture carries an invisible marker identifying it as made by AI. Draft saves and publication still need their separate permissions, enabled controls and human approvals. Opening the chat grants no additional access.

If chat does not appear, refresh after saving any pending editor work and try the top-header icon again. An access or feature-disabled message is different from a hidden panel: ask your administrator to check Mink availability and your permissions.

Get a daily or weekly business brief

Ask "What needs my attention in echos?", "Give me a weekly business overview" or "Give me a daily brief for Delhi." Mink prepares one private background brief. You need Analytics View, Products View, Inventory View and Orders View. Existing Mink access and credit rules apply to the chat; the queued brief uses no further Gemini calls. Drafting does not need to be enabled.

Daily means yesterday in your store timezone. Weekly means the last 7 completed local calendar days, compared with the preceding 7 completed days. Today's partial sales are excluded. The card shows the exact periods, timezone and location scope. Online or unassigned orders enter only an unrestricted store-wide scope. Inventory stays separate for each accessible active physical location, up to 50; choose one location for a larger estate.

Four fixed checks show Needs attention, No threshold triggered or Not enough data. Sales attention requires a decline of at least 20%, with at least 5 recognized orders and positive net sales in the previous period. Stock attention means any tracked SKU is low or out at a location, using the Inventory workspace thresholds and zero-or-negative out-of-stock rule. Stock held elsewhere does not hide local shortages; untracked stock is excluded.

Return activity counts return records opened in each period, excluding rejected and cancelled records, scoped by the original order location. It flags a rise of at least 50% with at least 5 preceding records. This is not a return rate. Failed-payment evidence counts orders created in the chosen period whose current payment status is failed; attention requires at least 3 such orders and at least 20% of created orders. This is not a gateway-attempt failure rate or the time a failure happened.

Inventory and payment status are current when collected. Source reads may finish at slightly different times. The brief reports evidence, not invented causes, forecasts or an all-clear. Review live records before acting. No business records are changed, no customer messages are sent, and asking for a daily brief does not enable a recurring schedule. Recurring watches are configured separately as described below.

The progress card supports cancellation and retry after failure. Refreshing does not start another run. Completion uses the existing private workflow notification. Permissions and captured location scope are checked again before every step; a narrowed scope cancels the brief rather than reusing broader evidence. If a data source fails, the run retries or reports failure instead of showing healthy zeroes. Reopen the conversation for the result, or request a new brief for fresher data.

Enable private recurring Mink watches

Open Watches in the Mink chat header, or ask "Keep an eye on stock at Delhi" or "Give me a business brief every Monday." Mink shows the watch setup page; a chat request alone never enables, changes or deletes a watch. Choose Business brief, Low or out-of-stock inventory, Sales decline, Rising return activity or Failed-payment orders. Select all currently accessible locations or one exact location, a daily or weekly time, and optional quiet hours. Review the settings and tick the explicit consent box before choosing Enable watch.

Watches are private to the admin who enabled them. Creation and resume require Mink access plus Analytics, Products, Inventory and Orders View. They use the same four fixed evidence rules described in the business brief section, not arbitrary custom thresholds. Daily financial evidence covers yesterday; weekly covers the last seven completed local days. Inventory is current at the time of the check, per physical location. Stock in Delhi cannot conceal an empty shelf at Shop. This is scheduled monitoring, not real-time incident detection.

The timezone, location IDs and default inventory threshold are captured when you enable the watch. New locations never join an existing watch automatically. Changes to assignments, archived locations or permissions stop broader evidence from being reused and pause the watch. Pause/delete remain available with dashboard access when Mink is disabled. To change a watch's schedule, scope or quiet hours, delete it and create a new reviewed watch.

A scheduled business brief notifies for each new reporting period. Other watches notify when attention first appears. Sales, returns and payment watches stay quiet through the same attention episode, then can alert again after a later check detects recovery followed by new attention. Inventory re-alerts when per-location low/out-of-stock counts change. It is not an individual-SKU change feed: swapping affected SKUs without changing those counts does not generate another alert. Insufficient data is not proof of recovery or an all-clear.

Quiet hours use the captured store timezone; overnight intervals are supported. Checks still run, but notifications wait until quiet hours end and pending changes coalesce. A later completed check with no attention clears an undelivered alert. Alerts are private in-app notifications only, with no metrics in the notification preview. Reopening the result checks permissions again. No email, SMS, WhatsApp message, customer communication or automatic business action is sent. Scheduled checks use no Gemini calls or additional AI credits; normal chat costs still apply.

There are at most 5 watches per admin and 20 per store, including paused watches. Each watch has at most one check in progress. The existing worker picks up at most five due watches per heartbeat; time is approximate and missed intervals are skipped without a catch-up burst. Missing local times during daylight-saving changes skip that occurrence; repeated times run only once on that local day. Quiet hours with identical start/end times are rejected.

Use Refresh watches to see the latest completed evidence, errors and next check time. Source failure retries through the background workflow; exhausted retries pause the watch rather than reporting healthy zeroes. Review the error and use Resume to schedule the next future check. Pause or Delete stops pending work and suppresses undelivered alerts; an alert already delivered cannot be recalled. Delete is irreversible in the UI. Terminal scheduled snapshots older than 30 days are pruned in bounded batches, except the latest/pending evidence; deleted watches, their audit events and scheduled snapshots are purged after 30 days. Existing notifications follow the normal notification retention policy.

Review and approve a response to a watch alert

In Mink AI, open Watches, then Suggested responses below a completed check. You can also ask "What should I do about the Delhi stock alert?" Mink can read and explain your response plans, but it cannot approve or dismiss them. Only the admin who owns the watch can see or approve its plans. No plan appears without an attention signal; an empty list is not an all-clear.

Plans use a fixed triage order: local stock availability, failed-payment orders, sales decline, then return activity. This is an operational review order, not an estimate of revenue, savings or causation. Each card shows its evidence, period, captured locations and timezone, expected benefit and limits. Monetary impact is unknown. A specific-signal watch offers only that signal; a Business brief watch can offer up to four.

Tick the consent box for the exact card and choose Approve investigation. This authorizes one read-only investigation, not business changes. Approval is bound to the evidence snapshot, watch version, captured scope and fixed limits. Plans expire 24 hours after the source check completes; a newer completed check or a changed watch invalidates an undecided old card. Refresh responses to review the latest evidence. Repeated approval of the same card returns the same workflow instead of running it twice. Dismiss hides approval for that snapshot; it does not pause the watch or dismiss future evidence.

The existing background worker collects fresh evidence for the approved daily or weekly window and current inventory. If the signal has recovered or evidence is insufficient, it explains that and does not invent a remedy. Inventory details show at most 20 SKU rows from at most 3 affected locations, prioritizing locations with more out-of-stock SKUs. Returns and failed payments show at most 20 records. Limited lists are labelled; use the dashboard for all records. Sales review compares recognized sales and orders; ask for a separate 7-, 30- or 90-day revenue investigation for deeper channel or product breakdowns. Returns are record counts, not a return rate; payment statuses are not provider attempt history. Customer names, email addresses and phone numbers are not included in response details.

Suggested next steps are not executed. Stock adjustments, prices, discounts, campaigns, customer messages and other business actions still require their existing individual permissions, exact targets, previews and approvals. This phase cannot move stock, issue refunds, retry payments or apply a remedy automatically. Approving a watch or investigation grants no ongoing business-write authority. There are no extra model calls or AI credits for this deterministic investigation.

There is at most one scheduled check or response running per watch. Its result card supports refresh and the existing cancel/retry controls. Source failures retry safely; no failed query becomes a healthy zero. Permissions, active locations and the approved watch version are rechecked before every step. Pause or Delete stops pending response work too; resuming a changed watch does not reauthorize an old investigation. An already completed read is not undone. The five most recent approved investigations remain available under Suggested responses while retained. Response decisions follow the source-watch snapshot retention: deleting a watch or pruning its source check eventually removes the decisions. Live deployment and the existing workflow heartbeat are required.

Approve private memories and review text documents

Open Mink AI and choose Memories in the chat header. Your memories belong only to your admin account in this store, not to every employee. You can save answer preferences, brand voice or business context. Add a title and exact text, choose 30, 90 or 365 days, tick the approval checkbox and choose Approve and save memory. You can keep up to 10 active memories, with an 80-character title and 600-character body. Do not save secrets, passwords, payment details or customer personal information. Saying "remember this" in chat does not save anything; Mink directs you to these controls.

Approved unexpired memories are included as untrusted reference data in your future chat turns. They are not live business facts, system rules, location scope or permission to act. Your current request takes precedence over a preference, and changing facts still need live tools. If your role, permissions or location bindings change, affected memories are not used until you edit and approve them again. Background watches and existing queued workflows do not receive memories. Saving has no separate credit charge; including context uses ordinary model input tokens and normal chat billing.

Edit lets you review the complete replacement text and renew retention. Changes in another tab cause a conflict rather than overwriting someone else's edit. Repeating the same save returns the same version. Delete removes the stored memory text; Delete all my memories affects only you in this store. Content-free deletion markers prevent old retries from recreating deleted memories. Expiry stops use immediately, even if the background worker is down; the existing workflow heartbeat removes expired text in bounded batches. Memories can still be inspected and deleted when Mink generation or invitations are disabled, provided you retain dashboard access.

Deletion cannot recall context already sent to an active model run or erase mentions in old conversation history. Start a new conversation and delete old conversations separately when needed. Provider retention is governed by StoreMink's AI provider agreements; deleting a StoreMink memory is not a provider-data deletion request.

Choose + (Add image or document) near the composer for one UTF-8 .txt or .md file up to 8 KiB and 3,000 characters. The file is read locally. Review and edit the text, remove sensitive information, tick its checkbox, then choose Add reviewed text to message. Nothing is sent until you send the resulting message. The combined message must fit 4,000 characters. The reviewed text is labelled untrusted source data and retained with the conversation under its existing history/deletion rules; it is not saved as a memory, media upload or searchable document library. Markdown and instruction-like content are text, not authority to call tools or approve actions. Files cannot silently change stock, send messages or publish a storefront.

One control adds files: choose + (Add image or document), or drop a file onto the message box. Short UTF-8 text and Markdown files are read on your own device; images and PDFs are extracted only after you consent. Spreadsheets, audio files, external web addresses and automatic document processing are not supported, and the microphone is for dictation rather than an audio attachment. Invalid encoding, binary content and oversized files are refused rather than quietly shortened. Use Discard to remove a file you have not added yet, or edit the message before sending.

Review an image or PDF, or dictate text

Use + (Add image or document) or drop one supported image, PDF, text or Markdown file onto the message box for review. The separate microphone starts Dictate message after browser permission. Speak normally, then pause briefly; StoreMink detects that you have finished and puts one editable transcript in the message box. Cancel discards pending dictation. It is not a voice attachment, and nothing is sent to Mink until you press Send. HTTPS and browser audio support are required; otherwise type your request.

Each file must be no larger than 2 MiB. Images support single-frame PNG, JPEG or WebP up to 12 megapixels; StoreMink strips image metadata and resizes them to at most 1600 pixels per side. PDFs support up to 10 pages; encrypted, damaged, active-content or form PDFs are rejected. The same + (Add image or document) control takes short UTF-8 text or Markdown files up to 8 KiB, which are read on your own device rather than sent for extraction. Audio files, video, spreadsheets and long documents are not attachments: use the microphone for dictation.

Remove secrets and unnecessary customer details first. Check the processing consent box and choose Process for review. This sends the file to StoreMink's AI provider before you send a chat message. Processing for review keeps no copy of the file: it does not become a media item or a saved memory, though the provider's retention policies still apply. Keeping an image is a separate, deliberate step. Choose Save to Media Library beside the attachment and the picture is stored in your own Media library exactly as if you had uploaded it there, and its address is added to your message so Mink can use it straight away. Processing and saving are independent: do either, both or neither. Cancelling cannot retract bytes already sent to the provider.

Review and correct extracted image or PDF text because it can omit or misread details; it is not a verified stock level or action approval. Confirm the reviewed text, then choose Add reviewed reference to message. Dictated words are already editable in the message box. Nothing is sent to the chatbot until you press Send. Extraction is limited to 3,000 characters and the combined chat message remains limited to 4,000 characters. Chat and follow-up turns receive only the reviewed text, not the original image or PDF.

Beta extraction deducts no AI credits but incurs provider usage. A separate chat request follows the existing read/draft/action charging rules. Shared processing limits are five requests per admin per minute, 30 per store per hour, 100 per store per day and a platform-wide limit. Failed, cancelled and duplicate attempts also consume limits. Processing has a 45-second deadline and rejects overly complex inputs or incomplete responses. It does not automatically retry. After a failure, wait and explicitly approve another attempt; provider work from a timed-out request might still have incurred usage.

If processing is unavailable, check that Mink AI is switched on for your store and that you hold the dashboard permissions this feature needs. Permission, capacity, safety and provider failures never silently fall back to another model, so a refusal is reported rather than answered from a weaker source. Keep using typed prompts or short text documents while you check, and contact StoreMink support if it stays unavailable.

Closing, discarding or changing conversations cancels pending local work; the microphone is stopped and local previews are released. Deleting a chat follows the existing conversation policy and does not retract earlier provider processing. Attaching a file does not save memories, publish storefronts, change stock or authorize any other action, and it never creates a picture: asking Mink for a new picture is a separate request you make in the chat. Saving an attached image to your Media library is your own upload: it changes nothing on your storefront, and putting that picture on a page is still a separate proposal you review and approve. Approval rules remain unchanged.

Microphone dictation

Choose the microphone and begin speaking. After you speak, pause briefly and StoreMink automatically converts the recording into one editable transcript in the message box. Choose Cancel before conversion finishes to discard the recording. Dictation does not send a chat request automatically.

Check and correct names, SKUs, locations and numbers before you press Send. The transcript is added once after conversion, so it does not repeat interim phrases while you speak. This is dictation, not a live voice conversation.

StoreMink sends the temporary microphone recording to its configured speech service and does not save it as an attachment, Media file or memory. The speech service may process it under its own privacy and retention terms. HTTPS, microphone permission and browser audio support are required; otherwise type the message.