> ## Documentation Index > Fetch the complete documentation index at: https://docs.tybritelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Agentic Commerce > Your in-app assistant can prepare gift cards, promotions, and dynamic-pricing rules from your store's own data — and you approve before anything goes live. # Agentic Commerce Your in-app assistant already sees your store — sales, catalogue, the traffic funnel, business health. Agentic commerce lets it act on what it sees. It can prepare the things it would otherwise only suggest — a gift card for a lapsed customer, a promotion on slow-moving stock, a dynamic-pricing rule that targets a customer segment — and it handles the reversible catalogue housekeeping outright. The line it never crosses is approval on anything that moves money. A gift card, a promotion, or a pricing rule arrives as a **draft you approve**; it is inert until you do. The organisational actions — creating a subcategory, enabling a category, tagging a product, grouping products into a collection — are reversible and happen directly. ## What it can do | Action | How it works | | :---------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Issue a gift card** | Prepared as a draft. Nothing is sent to the customer until you approve. | | **Create a promotion** | Prepared as a draft, in one of the four promotion types. Live once you approve. | | **Create a dynamic-pricing rule** | Prepared as a draft, targeting a category, product, collection, or customer segment. Takes effect once you approve. Available on plans that include dynamic pricing. | | **Organise your catalogue** | Reviews your categories and subcategories and tidies them: creates a subcategory (nesting it under the right parent rather than adding a redundant one), moves a subcategory to where it belongs, re-files a mis-categorised product, and enables categories that match what you sell. | | **Tag products** | Sets merchandising tags. | | **Build and manage a product collection** | Groups products into a curated collection (e.g. "Summer Picks", "Under \$50", or your dormant/slow-moving stock — it can read which products haven't sold) that your storefront can feature, and adds or removes members of an existing collection. The members are exactly the products it lists; it's created live, and shows on the homepage unless you say otherwise. | | **Write a blog post** | Writes a real article — a buying guide, a new-arrivals piece — around products you actually sell, with a summary and search title and description filled in. Saved as a draft under CMS; it goes live when you publish it. | | **Create a lookbook** | Builds a shoppable page around a theme: a styled scene featuring the products you named, with a clickable hotspot placed on each one it can find in the picture. Saved as a draft — check the positions, swap in your own photography if you prefer, then publish. | | **Design a banner or cover** | Creates or redraws the desktop and mobile artwork for a promotion, collection, blog post or lookbook you already have. Anything it creates gets artwork automatically, so this is for changing what's there. A post or lookbook cover is treated as editorial artwork — no price, no discount, no call-to-action. Uses media credits. | | **Suggest reorders** | Surfaces a ranked list of what to restock — a recommendation, not an order. | Base product prices are off limits — the assistant only ever touches dynamic-pricing *rules*, never a product's own price. Anything a plan doesn't include, or your role isn't permitted to do, it won't offer. Written content needs your storefront URL set first (CMS → Settings). The product links in a post are built against it, so without one they would only resolve on your own site and break as soon as the post is shared — the assistant says so and stops rather than writing a post that falls apart. A lookbook hotspot claims a product is *at that point in that picture*, so it is only ever placed from what is actually visible in the scene. A product the assistant cannot find in the frame is left off and reported, never dropped at a guess — a page with two hotspots that land beats one with five where three point at nothing. If a scene cannot be produced at all, the lookbook is still created, with your products confirmed against the catalogue and a plain note that they are not placed yet. ## Approving a draft A draft appears wherever you already manage that thing: a draft gift card on the **Gift Cards** page, a draft promotion under **Marketing**, a draft rule on the **Pricing** page — each marked as an AI draft with **Approve** and **Reject**. You can also approve it right in the chat when the assistant proposes it, and the assistant's launcher shows a small count when suggestions are waiting. Approving a gift card is the moment it issues and the customer is notified; approving a promotion or a rule is the moment it goes live. Rejecting dismisses the draft — you can always ask again. Approving an AI suggestion is its own permission, separate from the pages themselves. A store owner can grant a teammate — an admin, a marketer — the authority to approve suggestions without changing anything else about what they can do. The check is enforced on the server, not just hidden in the interface. ## Margin protection Every value the assistant proposes is in your store's currency, and every money action protects your margin. It reads each product's cost to make sure a discount never sells below cost, and it prefers higher-margin or slow-moving stock. When too many products have no cost price set, margin can't be trusted — so the assistant declines to prepare any gift card, promotion, or pricing rule and points you to **Inventory → Bulk Edit** to fill in the missing costs first. This is deliberate: a campaign that looks good but sells below cost is a real loss, and the assistant would rather ask you to set costs than risk it. The reversible catalogue actions stay available in the meantime. ## Dynamic workflows Everything above happens once, when asked, and the intent ends with the conversation. A **dynamic workflow** is the same intent kept running: ask for something ongoing — "keep my featured collection showing what's actually selling", "every week, check for slow stock" — and it becomes a rule that re-evaluates on a schedule. They are dynamic rather than fixed: each evaluation re-reads the store's current figures and decides whether anything warrants doing, so the outcome follows the business rather than a predetermined sequence — the same workflow features different products as the sales change. This is what distinguishes them from [event-driven automations](/workflows/webhooks-automation), where a defined action follows a specific event. The split is unchanged. Reversible merchandising runs unattended: rotating a collection to current best sellers, retiring members that stopped selling, tagging what sells. Anything touching money still only prepares a draft and waits for approval, exactly as a conversation would — promotions and clearances, gift cards for customers who pass a spending threshold in a window, and markdown pricing rules over stock that stopped moving. The money templates carry limits the reversible ones do not, in proportion to what they touch. A promotion template drafts one promotion; a gift-card template drafts one card per qualifying customer, and a gift card is a liability the merchant owes. So a single run is capped on both the number of recipients and their combined face value, and a rule matching more customers than the cap allows stops and reports that rather than silently drafting an arbitrary subset. A cooldown keeps the same customer from being rewarded again on the following run. A markdown rule is scoped to the specific products it identified rather than the whole catalogue, is drafted switched off, and leaves only one draft outstanding at a time so a weekly cadence cannot stack duplicates while the merchant decides. Every one of these limits is enforced in the database, not in the prompt. ### Content on a schedule Writing is a standing intent too: ask for a post or a lookbook on a recurring basis and each run produces a new one — a real piece, built around products you actually sell, with a cover image, saved as a draft under CMS. Nothing is published for you; it is your public voice, so you publish it. Give the rule either a fixed topic or a **category**. With a category it chooses its subject afresh every run from whatever shoppers are most drawn to there, so the piece follows real demand instead of repeating something you decided months ago. If nothing in that category drew interest that week, it writes nothing and tells you why. These run weekly at most, and a rule pauses itself once three of its drafts are waiting unread — publishing or discarding some starts it again. ### Seasons and days Any workflow can be scoped to part of the year and to particular weekdays — promotions, collections, tagging, gift cards, pricing and content alike, not only the writing ones. A **season** recurs. Set up a Black Friday rule for November or a Valentine's rule for February once, and it wakes every year on its own; out of season it is skipped rather than switched off, so it comes back without you re-enabling it, keeping its name, settings and history instead of being deleted and rebuilt each year. A window can wrap the year end, for a mid-December to early-January run. **Weekdays** pin a rule to the days you mean. On its own a weekly rule is an interval, so it drifts by a day or so each time; naming Friday makes it land on Friday and stay there. They combine: | You want | How it is set up | | :------------------------------------------------------------------------------------- | :---------------------------------------------------- | | A lookbook every Friday in December, featuring whatever is most in demand in Wearables | Weekly · Fridays · 1–31 December · category Wearables | | A clearance draft every year in the first week of January | Weekly · 1–7 January | | A post about new arrivals every week, all year | Weekly · no season | | Featured rotated to current best sellers every Monday | Weekly · Mondays | Dynamic workflows are managed at **Settings → Workflows**, which is also where each one can be paused or removed. Alongside the configuration is the record of every run — what it did, and the figures behind the decision, so a change always has an explanation attached rather than appearing unannounced. A workflow that fails repeatedly switches itself off and says so, rather than retrying indefinitely. ## Human in the loop, by design The assistant proposes; you decide. It never issues a gift card, activates a promotion, or turns on a pricing rule on its own — and it cannot be talked into bypassing the margin check or the approval step, because those are enforced in Galactic Core's own code rather than left to the assistant's judgement. Those checks are part of a wider set of platform [guardrails](/how-gc-works/guardrails). Every action it takes is recorded in your activity log under its own name, so an AI-assisted change is as traceable as a manual one.