# What the plugin can do The plugin covers seven capability areas. Everything is included with your MixShift subscription; the plugin is in beta. ## Explore your warehouse Ask questions against your MixShift data warehouse in plain English: Sponsored Products, Brands, and Display, DSP, Seller Central and Vendor Central revenue and orders, inventory, and catalog. Results export to CSV on request, and large results save as files automatically. The warehouse connection is read-only at the database level. ## Pull reports from Amazon, on demand Request reports straight from Amazon for any merchant and window you are authorized for: orders, listings, FBA inventory and fees, returns, settlement, Sales and Traffic, Brand Analytics (including Search Query Performance), and Vendor Central reports. Useful when you need data MixShift does not already hold, or a known report for an ad-hoc time frame. ## Look up live retail state Fast point-in-time answers about your catalog, inventory, FBA inbound shipments (down to tracking, boxes, pallets, carrier and placement fees), orders, finances, pricing, Subscribe & Save, product reviews, listings, and your live promotions (coupons, deals, price discounts, and basket-building offers, for seller accounts), served live from Amazon rather than from a generated report. ## Run clean-room and DSP analytics Amazon Marketing Cloud queries in plain English with CSV results, and audiences built from a description ([how it works](/knowledge-base/plugin/how-to/run-amc-queries-from-claude)), DSP report pulls (including DSP performance older than 90 days, or a monthly history in one request), and DSP account reads for the accounts you are connected to: which campaigns and creatives exist, which creative is attached to which line item, whether a placement is running, paused, or was rejected and why, which creatives are eligible for a given line item, and discovering the account's DSP advertiser id. Reports and account reads are read-only. DSP campaigns and ad groups can be changed (a campaign's state, budget caps and flights; an ad group's state, budget, dates, bid and pacing), and those changes preview first like every advertising write. Creating creatives, attaching them to ad groups and changing placements still happen in the Amazon DSP console. ## Manage advertising, with guardrails Live reads of campaigns, bids, budgets, and recommendations, plus the analytical tier: daily health checks, runaway-spend detection, bid reviews, search-term negation and harvesting, portfolio triage, and the monthly report. Analytical skills read your brand context; see [Set up a brand](/knowledge-base/plugin/how-to/set-up-a-brand). Writes exist and are deliberately narrow: advertising changes (pause and enable, bids, budgets, keywords, targets, negatives, Amazon DSP campaigns and ad groups, and Amazon Marketing Cloud audiences) preview first, show you the exact change set, and reach Amazon only after you confirm. Every change is recorded in an audit trail. If you decline a preview, nothing is sent. A change can also be saved as a proposal instead of being applied: a person on your team reviews it later, and it reaches Amazon only after they approve and commit it. A proposal expires if nobody acts, and is refused rather than applied if the live values changed since it was written. Walmart ads follow the same contract in beta: once your Walmart Connect advertiser is connected to your MixShift account, you can read your Walmart campaigns and their last 30 days of performance, and changes to campaigns, keywords and bids preview first and reach Walmart only after you confirm. To connect one, an admin on your Walmart ad account adds MixShift as a partner in Walmart Connect Ad Center (Access, then Partners, then + Add Partner; see Walmart's guide, [Account access as an admin user](https://advertisinghelp.walmart.com/s/guides?language=en_US&article=000012444)) and emails the advertiser ID to support@mixshift.io. MixShift links it to your account and tells you when it is live. ## Forecast what comes next Forecasting is a [MixShift Intelligence](/knowledge-base/intelligence) service; see [Get a forecast with Forecast Max](/knowledge-base/intelligence/how-to/get-a-forecast) for the full walkthrough. Ask what to expect from a brand next quarter and the plugin checks that the account has the history for a forecast, then explains the forecast in plain language with its measured accuracy and what it stands on. When the [MixShift forecasting app](https://forecast.mixshift.ai/) has published a forecast for the account, that is what you get, corrections included. When it has not, you get a forecast computed from your warehouse history with the same engine, clearly labelled as computed. If you have a sponsored ads budget for the coming months, the plugin can save it (`mixshift forecast budget set`, with `show` and `clear` to check and undo) and run the forecast again on your numbers; the answer then says month by month whether the spend is your budget or an estimate. When one Amazon account carries several brands, ask for the one you mean and it forecasts that brand alone, after confirming the brand's product and campaign labels with you (`mixshift forecast sub-brand list`, `add` and `remove` manage these brands). ## Remember your brand A brand timeline records events that matter (launches, price changes, stockouts) so reports can explain movements instead of just charting them. Brand context publishes to your organization store automatically, from a brand's first setup onward rather than only once someone has shared it by hand, and the events recorded on a brand travel to the timeline with it, so the whole team works from the same memory. Every automatic share prints a notice in the chat, and automatic publishing can be turned off if you would rather share on request. Arrival is automatic too: the first time anyone on the team works an account that was set up elsewhere, its context reaches that machine in the background, with no pull step to remember. When the team stops working a brand, you can [retire it](/knowledge-base/plugin/how-to/set-up-a-brand): it stops showing as active for everyone, nothing is deleted, reports still include it, and restoring it brings it back. ## The boundaries, plainly - **The warehouse is read-only. Always.** The database user cannot write, so no chat instruction can change warehouse data. - **Advertising is the only surface that writes to Amazon**, and every write is preview-gated and audited. All other Amazon surfaces in the plugin are read-only. Walmart ads, in beta, also write only through a preview you confirm. - **The forecast skill saves one thing, in MixShift only:** your monthly sponsored ads budget, and only after you have seen the months and amounts and said yes. - **Analytical skills need brand setup first.** Exploration and reports work with sign-in alone. - **Everyone in your MixShift org sees the same brands.** Per-user data scoping is not available today. - **One MixShift organization per sign-in.** An agency working across several MixShift customer accounts switches by signing in to the other account. - **MixShift Intelligence is open to every account.** Monthly Report Max and the `mixshift intelligence` commands use it, and you can run and validate a bridge yourself in the [Intelligence Workspace](https://hcam.mixshift.ai/); see the [Intelligence knowledge base](/knowledge-base/intelligence). - **During beta, usage telemetry is attributed** (account and person) so we can fix what breaks quickly. The plugin repository documents exactly what is and is not collected, and how to opt out. ## Related - [Skill catalog](/knowledge-base/plugin/reference/skill-catalog) - [Run a skill](/knowledge-base/plugin/how-to/run-a-skill) - [Builder Platform](/knowledge-base/builder-platform) (the same data from your own code and other AI tools)