Prompts and skills for marketplace reporting

Review sales, investigate a change or take a closer look at ad spend. Start with a prompt, then keep the method as a reusable skill.

Browse prompts

New to MerchantSpring? Book a demo

Questions for your next review

Sales & account reviews

See where sales are shifting

Compare sales across your channels and see which accounts contributed most to growth or decline.

By the MerchantSpring team

Prepare your weekly sales review

Bring one channel’s sales, product highlights and open questions into a review for your team.

By Abhi at MerchantSpring

Investigate product sales changes

Find the products behind a sales change, or examine a specific SKU or ASIN.

By Abhi at MerchantSpring

Marketplace account audit

Review available sales, advertising, profit and operating data to set account priorities.

By the MerchantSpring team

Check readiness for a sales event

Bring stock, advertising and listing checks into a dated plan for your next sales event.

By the MerchantSpring team

Advertising

Audit your PPC performance

Compare campaign spend with attributed sales and your targets, then decide what to investigate or test next.

By Abhi at MerchantSpring

Spot keywords worth reviewing

Find keywords with spend and no reported orders, using the spend and click thresholds you choose.

By the MerchantSpring team

Find search-term opportunities

Find converting search terms to review as targets and zero-order terms that may need closer attention.

By the MerchantSpring team

Advertising placement performance

Compare click costs and attributed results across placements within each campaign.

By the MerchantSpring team

Hourly advertising performance

Review hourly ad results and see whether a recurring pattern is worth testing against your campaign goals.

By the MerchantSpring team

Search & brand analytics

Search Query Performance opportunities

Find queries with gaps between your impression, click and purchase shares.

By the MerchantSpring team

Brand Analytics review

Review product engagement and repeat purchases in the available Brand Analytics reports.

By the MerchantSpring team

Profit & inventory

Profit and margin review

Break down revenue and included costs to explain product or channel margins.

By the MerchantSpring team

Inventory cover and replenishment risks

Spot products that could run out before replenishment arrives, and check the stock and delivery dates behind the risk.

By the MerchantSpring team

Listings & account health

Prioritise account-health issues

Turn account-health and policy notices into a list of priorities, deadlines and next steps.

By the MerchantSpring team

Review listing quality

Review your listing for clarity, useful product details and points to check against the applicable rules.

By the MerchantSpring team

Draft clearer listing copy

Draft titles, highlights and bullets from verified product facts, with character counts and a checklist for review.

By the MerchantSpring team

Getting started

Explore what you can ask through MCP

Check the reports available through your MerchantSpring connection and choose a matching workflow.

By the MerchantSpring team

See where sales are shifting

By the MerchantSpring team

Compare sales across your channels and see which accounts contributed most to growth or decline.

What you’ll get

  • A compact scope statement and separate comparison tables for incompatible groups.
  • Prior sales, current sales, absolute change and percentage change by channel, plus the largest rises and falls.
  • Reconciled group movement where supported, with any excluded channels or incomplete coverage clearly identified.
  • Up to three investigation priorities, each tied to a number and a useful next check.

Your inputs

  • Choose the accounts or channels, or retain all accessible channels.
  • Set both periods; the default is the last two completed Monday-Sunday weeks.
  • Specify the reporting timezone and currency if these are not established by the reports.
  • Use channel-sales reports available through your connection, or supply readable reports for both periods with channel IDs and metric definitions.

Reports to use

  • Channel or store identifiers and sales values for both periods, with currency and sales definition.
  • Enough channel metadata to distinguish separate stores from overlapping views of the same store.

Optional inputs

  • Channel type, country and explicitly reported units or orders.
  • Customer-supplied priorities or a materiality threshold for the investigation shortlist.

Next question

For the channel with the largest verified decline, show the products contributing to that change and how much of the channel movement the available breakdown explains.

Prepare your weekly sales review

By Abhi at MerchantSpring

Bring one channel’s sales, product highlights and open questions into a review for your team.

What you’ll get

  • A short headline with exact weeks, channel, sales measure, current result and change.
  • A small KPI table, with target comparison only when compatible targets are supplied.
  • Product highlights with a note on how the breakdown reconciles to channel sales and which products are covered.
  • Up to three specific questions for the next review, each connected to an observed result.

Your inputs

  • Choose one marketplace or store channel.
  • Set the two weeks and reporting timezone, or keep the completed-week default.
  • Name the intended reader and any specific question they need to resolve.
  • Provide a compatible target only if a target comparison is wanted.
  • Use channel-sales reports available through your connection, or supply readable reports. Add product reports when you want a breakdown of the changes.

Reports to use

  • One channel's sales for both weeks using the same reporting measure.

Optional inputs

  • Units or orders for both weeks, with definitions.
  • Product sales for both weeks using the channel total's basis.
  • A weekly sales target or explicitly documented business events supplied by the user.

Next question

For the largest product decline in this review, investigate whether the available traffic, units, advertising and availability evidence narrows the possible explanations.

Investigate product sales changes

By Abhi at MerchantSpring

Find the products behind a sales change, or examine a specific SKU or ASIN.

What you’ll get

  • The chosen review mode, product identifiers and reporting scope.
  • A contributor table or selected-product before/after scorecard with figures and changes.
  • A reconciliation or coverage note; an optional units/sales-per-unit bridge when valid.
  • Supporting evidence from requested compatible modules, with missing modules identified.
  • A concise explanation of the findings, possible causes and next checks.

Your inputs

  • Choose the channel and both comparison periods.
  • Choose contributor ranking or name the specific product to investigate.
  • For a named product, identify whether it is a SKU, child ASIN, parent ASIN or another product ID.
  • Optionally request traffic, advertising, availability or margin checks where compatible evidence exists.
  • Use product reports available through your connection, or supply readable reports with metric definitions. Add supporting reports for the questions you want to explore.

Reports to use

  • Product identifiers and comparable sales values for both periods, covering the requested products.
  • An explicit mapping where the user's product identifier differs from the report's row identifier.

Optional inputs

  • Compatible channel totals to measure how much of the channel change the product breakdown covers.
  • Units, orders, sessions or traffic measures with documented numerator/denominator relationships.
  • Product-level advertising, dated availability history, or product P&L with complete cost definitions.

Next question

Take the strongest remaining explanation from this review and identify the specific additional report or comparison that would help confirm or reject it.

Audit your PPC performance

By Abhi at MerchantSpring

Compare campaign spend with attributed sales and your targets, then decide what to investigate or test next.

What you’ll get

  • An audit summary that states the objective, included campaigns/products, periods and attribution status.
  • Campaign and compatible-group tables with spend, attributed results, changes and correctly aggregated rates.
  • A prioritised review queue with evidence, target context and next checks.
  • Supporting detail where available, with the reports or fields needed to complete any remaining checks.

Your inputs

  • Choose the advertising account/channel and the ad products to include.
  • Set both periods; retain completed months if appropriate for the decision.
  • Name the objective and any target, with campaign-specific targets where relevant.
  • Provide the report's attribution basis and extraction date where available.
  • Use campaign reports available through your connection, or supply readable reports with campaign IDs, spend and attributed results. Add supporting reports for a closer look.

Reports to use

  • Campaign IDs, spend and attributed sales for the periods being compared, with advertising product and attribution definitions.
  • A stated business objective, with a numerical target if one has been set. Ask for a target when needed; do not invent one.

Optional inputs

  • Impressions, clicks and attributed orders on the same reporting basis.
  • User-supplied campaign targets, lifecycle or brand/nonbrand classifications.
  • Compatible ad-group, product or placement detail; actual budget/serving evidence; product availability and complete margin inputs.

Next question

For the highest-priority campaign, inspect the available ad-group, product or placement detail and propose one evidence-based test with a clear measurement rule.

Spot keywords worth reviewing

By the MerchantSpring team

Find keywords with spend and no reported orders, using the spend and click thresholds you choose.

What you’ll get

  • The exact selection rule, report scope, period and attribution status.
  • A ranked shortlist with keyword context, spend, clicks, explicit order count and matched threshold.
  • The qualifying spend subtotal and a separate list/count of unresolved order data.
  • A useful next check and any prior-period evidence for the leading rows.

Your inputs

  • Choose the channel, ad product and reporting period.
  • Set a minimum spend, minimum clicks or both, and say whether multiple conditions use AND or OR.
  • Provide the attribution basis and extraction date where available.
  • Use a keyword-performance report available through your connection, or supply a readable export. Choose the search-term or SQP workflow for those report types.

Reports to use

  • Keyword-level rows with spend and explicitly reported attributed order/purchase counts.
  • Stable keyword identity plus campaign/ad-group context sufficient to distinguish repeated keyword text.
  • Clicks when the selected threshold uses clicks.

Optional inputs

  • Match type, campaign status and CPC inputs.
  • Prior-period keyword results on the same basis to check persistence.
  • Product relevance, margin or campaign-purpose context supplied by the user.

Next question

Compare the shortlisted keyword IDs with the preceding complete period on the same basis and show which zero-order patterns persisted before proposing a review action.

Marketplace account audit

By the MerchantSpring team

Review available sales, advertising, profit and operating data to set account priorities.

What you’ll get

  • Executive assessment with the most important decisions and supporting figures.
  • Module coverage table including modules not assessed and why.
  • Sales bridge and focused advertising, profit and operating findings where supported.
  • Prioritised decision table: issue, evidence, likely impact, confidence, next check and proposed owner.
  • Source and comparison notes sufficient to reproduce the review.

Your inputs

  • Name the account, marketplace and any product exclusions.
  • Provide the review and comparison dates, currency and business objective.
  • Identify the decisions the review should inform, such as margin recovery, growth or operational fixes.
  • Add known launches, promotions, price changes and stock interruptions with dates.

Reports to use

  • Sales values for the selected account, scope and comparison periods.
  • Definitions of the sales basis, currency, period and available reporting coverage.

Optional inputs

  • Compatible order and unit counts, plus product or category reports with stable identifiers, for volume, order-value and product-contribution analysis.
  • Advertising spend and attributed outcomes with attribution settings.
  • Profitability components and COGS coverage.
  • Inventory, Buy Box, listing restrictions, seller health, traffic or Brand Analytics reports where available.

Next question

Investigate the highest-priority issue using the available product and daily data, and show what evidence would confirm or reject each explanation.

Search Query Performance opportunities

By the MerchantSpring team

Find queries with gaps between your impression, click and purchase shares.

What you’ll get

  • Query opportunity table with scope, counts/shares, stage gaps and comparison changes.
  • Separate branded and nonbranded findings with uncertain classifications shown.
  • A short prioritised investigation list tied to actual products and queries.
  • Report periods, coverage and notes on how the SQP measures relate to advertising attribution.

Your inputs

  • Identify the marketplace, brand or ASIN view, and exact ASIN list.
  • Specify valid complete reporting periods and the comparison.
  • Provide SQP fields or exports including query totals and your corresponding counts or shares.
  • Identify known branded queries or brand aliases; label uncertain classifications.

Reports to use

  • SQP query identifier/text, report period and verified brand or ASIN scope.
  • Query total and corresponding brand/ASIN counts or reported shares for the funnel stages being assessed.

Optional inputs

  • Search query volume, cart adds, median prices and shipping-speed fields.
  • Comparable prior SQP periods.
  • Relevant paid search-term reports, offer details and inventory history for separate follow-up.

Next question

Investigate the highest-volume query with a purchase-share gap using available price, availability and relevant paid search-term evidence.

Brand Analytics review

By the MerchantSpring team

Review product engagement and repeat purchases in the available Brand Analytics reports.

What you’ll get

  • Module coverage and eligibility summary.
  • ASIN-level funnel comparison with counts, denominators and meaningful changes.
  • Separate repeat-purchase or other supplied-module findings.
  • Prioritised product or customer questions with evidence and next tests.
  • Notes on which reports can be compared and how to interpret the customer measures.

Your inputs

  • Specify the brand, marketplace, ASIN scope and valid reporting period.
  • Choose the commercial question and comparison period.
  • Provide available Brand Analytics exports or identify the accessible reports.
  • Add product launches, replenishment cycles or promotion context where relevant.

Reports to use

  • At least one complete eligible Brand Analytics report with its period, metric definitions and ASIN or query scope.
  • Catalog-to-ASIN mapping for product-level conclusions; repeat-purchase definitions if that module is supplied.

Optional inputs

  • Search Catalog Performance, Repeat Purchase, Market Basket Analysis and Top Search Terms reports, each separately scoped.
  • Search Query Performance for a selected query follow-up.
  • Product availability, prices and listing-change history for testing explanations.

Next question

Take the product with the clearest funnel deterioration and compare its relevant search queries, price and availability over the same valid periods.

Profit and margin review

By the MerchantSpring team

Break down revenue and included costs to explain product or channel margins.

What you’ll get

  • Profit bridge from revenue through each included cost category.
  • Profit and margin by comparable product/channel with aggregate reconciliation.
  • COGS and expense coverage, including unallocated costs and partial margins.
  • Prioritised margin drivers and clearly labelled commercial scenarios.
  • Accounting, timing and returned-cost settings used.

Your inputs

  • Specify channel and product scope, currency, tax treatment and accounting/report basis.
  • Provide the review dates and comparison dates.
  • Identify whether advertising, shipping, overhead and returned-COGS credits are included.
  • Supply COGS with currency and effective dates, or identify the coverage gaps.

Reports to use

  • Net revenue or the component revenue, refunds and discounts needed to derive it on a documented basis.
  • Fees, fulfilment/shipping and other reported expenses with sign conventions; advertising spend if included in the requested margin.
  • COGS coverage and effective dates, including a clear statement when costs are missing.

Optional inputs

  • Product-level breakdown and channel-level reconciliation.
  • Refund, reimbursement and adjustment details.
  • Units sold, cost-change history, margin targets and known one-off expenses.

Next question

Model a change for the largest margin driver, showing the current result, assumptions and break-even conditions without changing prices or campaigns.

Inventory cover and replenishment risks

By the MerchantSpring team

Spot products that could run out before replenishment arrives, and check the stock and delivery dates behind the risk.

What you’ll get

  • SKU risk table with current stock, demand basis, cover, lead time, inbound timing and priority reason.
  • Dated projected shortages and arrivals under the stated scenario.
  • Replenishment quantity scenarios with formulas, assumptions and pack rules.
  • Missing inputs and sensitivity to demand or delivery changes.

Your inputs

  • Specify the inventory snapshot date, marketplace and SKU scope.
  • Provide daily demand or the existing forecast with its windows and weights.
  • Provide replenishment lead time including receiving, and any safety-buffer or target-cover setting.
  • List inbound quantities, expected availability dates and known supply delays.
  • Note promotions, stockouts, seasonal changes and order-pack constraints.

Reports to use

  • Stock by stable SKU and status, with available/sellable quantities distinguished from reserved, inbound and unfulfillable stock.
  • A documented daily demand rate or enough sales history to calculate a labelled baseline.
  • Lead times and planning targets for assessing replenishment urgency; without these, only descriptive cover can be given.

Optional inputs

  • Dated inbound supply, committed demand not already deducted and supplier pack sizes.
  • Stockout history, seasonal/promotion plans and forecast settings.
  • Inventory age, storage costs and product margin for slow-stock decisions.

Next question

Compare the urgent SKUs under the current arrival dates and a [number]-day delivery delay, using the same documented demand assumptions.

Find search-term opportunities

By the MerchantSpring team

Find converting search terms to review as targets and zero-order terms that may need closer attention.

What you’ll get

  • Scope and coverage summary, attribution maturity, field definitions and the agreed screening thresholds.
  • A candidate table with raw term, supported product/campaign/ad-group identity, clicks, purchases, spend, sales, calculated rates, evidence status and rationale.
  • Separate lists for targeting tests, negative-target review and insufficient-evidence rows; show proposed match type and scope only where justified.
  • Checks still needed before a person changes targeting, plus a follow-up measurement period tied to the relevant attribution window.

Your inputs

  • Account, marketplace, campaign types and any campaign or product scope.
  • Exact reporting period, extraction date and attribution window used by each conversion field.
  • Target ACoS or campaign objective; minimum evidence thresholds are user choices, not universal rules.
  • Product relevance, launch/defensive strategy, and any terms or brands that must be retained.
  • Use a search-term report available through your connection, or supply a readable export with the required fields.

Reports to use

  • Actual search-term rows with account/marketplace, campaign/ad-group identity, campaign type, target or targeting expression and match type where supplied, clicks, spend, attributed purchases and sales.
  • Report definitions identifying attribution window, click/view basis, date basis, units versus purchases, and whether reported terms are typed queries or inferred contexts.
  • Product or ASIN identity where supplied by the report. Otherwise, keep the analysis at the supported campaign and ad-group level.

Optional inputs

  • Existing keyword and negative-target lists, including match type, status and campaign/ad-group scope.
  • Advertised-product and purchased-product reports with documented join keys; product relevance, margin and inventory context.
  • A comparable earlier mature period to distinguish persistent patterns from one-period noise.

Next question

Compare the proposed candidates with our existing targets and identify duplicates or potentially harmful exclusions before we review any changes.

Advertising placement performance

By the MerchantSpring team

Compare click costs and attributed results across placements within each campaign.

What you’ll get

  • Placement comparison table with base counts and calculated ratios.
  • Campaign-level findings that explain mix, volume and attribution limits.
  • Proposed tests with rationale, measurement and required settings.
  • Reconciliation and any placement groups excluded to prevent double counting.

Your inputs

  • Specify account, marketplace, campaign IDs and ad product.
  • Provide the reporting dates and consistent attribution window.
  • Provide the placement report and campaign objectives or targets.
  • Add bidding strategy and placement/audience settings if bid scenarios are requested.

Reports to use

  • Campaign and placement identifiers, spend and attributed sales with consistent attribution definitions.
  • Clicks and impressions for traffic efficiency; attributed order counts if a purchase-to-click measure is needed.

Optional inputs

  • Comparable prior periods, budget availability and configuration/change history.
  • Product margin, stock availability and campaign targeting/mix.
  • Explicit business performance targets and bid constraints.

Next question

For the campaign with the clearest placement trade-off, prepare a test using its actual bidding strategy, modifiers, margin target and recent performance.

Hourly advertising performance

By the MerchantSpring team

Review hourly ad results and see whether a recurring pattern is worth testing against your campaign goals.

What you’ll get

  • Hourly or time-window table with timezone, observations, spend, outcomes and weighted efficiency.
  • Notes on whether patterns repeat, hourly coverage and attribution timing.
  • Potential test windows with evidence and alternative explanations.
  • A review-ready test plan and the extra data needed before making changes.

Your inputs

  • Provide an hourly report with the campaign scope and reporting timezone.
  • Specify the date range, attribution window and reporting as-of date.
  • Identify whether the hour represents ad interaction, conversion event or another documented event.
  • Add budget exhaustion, schedule, bid-change, promotion and stock history where available.

Reports to use

  • Documented hourly campaign records containing the hour field, spend, clicks and attributable outcome fields used for efficiency analysis.
  • Timezone, attribution window, event-time basis and rules for how records are updated.
  • Enough comparable hourly observations to describe the observed pattern; report sparse coverage rather than prescribing a universal minimum.

Optional inputs

  • Impressions, orders, budget status and placement/targeting dimensions.
  • Bid/schedule history, promotions, stock availability and business targets.
  • Repeated comparable weeks and a separate holdout period for testing pattern stability.

Next question

Check whether the proposed hourly pattern remains in the next comparable period, keeping campaign scope, attribution maturity and timezone consistent.

Put paid sales in context

By the MerchantSpring team

Review ad spend alongside attributed sales and total sales, using the right definitions for each comparison.

What you’ll get

  • A clear statement of what the reports support: a reconciled source split, a contextual comparison, or a request for matching data before comparison.
  • A compact compatibility table and separately labelled retail, spend and attributed-sales metrics.
  • Current versus comparison results with the exact formulas and metric bases used.
  • Evidence-backed observations, unresolved hypotheses and the additional report required for a stronger answer.

Your inputs

  • Retail account/marketplace and advertising profile identities, with seller versus vendor specified.
  • Exact current and comparison periods, timezone, currency, extraction dates and retail revenue definition.
  • Advertising campaign types, interaction types and attribution windows included.
  • Product scope and whether each ad report is grouped by advertised ASIN or purchased ASIN.
  • Choose the question: describe spend relative to retail sales, investigate a change, or assess a source-of-sales breakdown.

Reports to use

  • Retail sales for the specified account and product population with date, tax, discounts, returns and order/shipment basis documented.
  • Ad spend and attributed sales with campaign type, attribution window, click/view inclusion, date basis and product/merchant coverage.
  • Identity mapping sufficient to establish which retail and advertising scopes can be compared.

Optional inputs

  • Purchased-product reporting or documented transaction-level attribution with mutually exclusive sources and compatible conversion dates.
  • Prior comparable periods, traffic, Featured Offer, inventory and price/promotion history for investigating co-occurring changes.
  • An explicit independently measured organic-sales field, with its methodology and coverage.

Next question

Check whether our available purchased-product and date-basis data can support a closer reconciliation for the products driving this change.

Prioritise account-health issues

By the MerchantSpring team

Turn account-health and policy notices into a list of priorities, deadlines and next steps.

What you’ll get

  • The account and date reviewed, sources used and status reported by each source.
  • An issue list with the source of each severity rating, deadlines, case or ASIN identifiers, responsible owner where supplied and next action.
  • A performance table separating reported and recalculated rates, eligible counts, metric windows and applicable targets.
  • Missing evidence and what must be confirmed in the authoritative account before an issue can be considered resolved.

Your inputs

  • Seller account, marketplace and report snapshot time.
  • Readable AHR/performance export or screenshots, plus relevant policy-violation notices with case IDs and dates.
  • Metric windows, numerators/denominators and targets shown in the source, where supplied.
  • Current official marketplace policy links or readable policy text if access is restricted.
  • Any already completed corrective actions, submission statuses and responsible owners.

Reports to use

  • At least one actual account-health, performance or violation report/notice with account, marketplace and snapshot/date context.
  • For threshold-based conclusions, the applicable current official threshold or target displayed by the source, its effective context and the relevant metric definition.

Optional inputs

  • Order-level defects and eligibility counts for reconciling performance rates.
  • Earlier snapshots, unresolved notices, appeal/submission history and evidence of accepted resolutions.
  • Accessible listing-status data for the named affected ASINs.

Next question

Build an evidence checklist for the highest-priority open issue using the notice's exact requirements and our documented corrective actions.

Review listing quality

By the MerchantSpring team

Review your listing for clarity, useful product details and points to check against the applicable rules.

What you’ll get

  • Fields inspected and evidence sources, with any additional material needed to complete the review.
  • Prioritised findings with field/image reference, evidence, category of issue and suggested correction.
  • A product-fact conflict list and any policy questions requiring current authoritative confirmation.
  • A short rewrite brief for the selected fields, without publishing or implying verified commercial impact.

Your inputs

  • Product identity, marketplace, category, language and capture date.
  • Readable current title, Item Highlights if present, bullets, description and any requested backend fields.
  • Product fact sheet, variant details and evidence for claims.
  • Provide readable image files or accessible images for visual review; filenames identify files but do not provide their visual content.
  • Applicable current official category/marketplace guidelines, or readable excerpts if access is restricted.

Reports to use

  • The actual listing fields to be reviewed, plus product identity and marketplace/category context.
  • An authoritative product fact source to distinguish verified characteristics from unsupported claims.
  • Current applicable official rules for any specific policy or character-limit finding.

Optional inputs

  • Readable product images, packaging, dimensions and image-role labels.
  • Search-term/SQP evidence with dates and product scope to inform relevant language without promising ranking outcomes.
  • Supplied backend search terms, variation family data, customer questions or verified listing-suppression notices.

Next question

Use the verified product facts and this review to draft replacement copy for the highest-priority fields.

Draft clearer listing copy

By the MerchantSpring team

Draft titles, highlights and bullets from verified product facts, with character counts and a checklist for review.

What you’ll get

  • Recommended draft for each requested field with character count and applicable limit where verified.
  • A brief explanation of the product information prioritised and any important wording choice.
  • Sources for the product claims and a review checklist covering facts, variant accuracy, policy and field availability.
  • A clear draft status and unresolved checks; no claim of publication, approval by Amazon or predicted ranking uplift.

Your inputs

  • Exact product/variant, marketplace, category and language.
  • Fields to draft, current copy and requested tone or brand conventions.
  • Approved product facts, care/compatibility requirements and evidence supporting any claim.
  • Current applicable field limits and category rules, with official source or readable supplied policy.
  • Optional relevant query evidence; specify any required terms only if accurate for this product.

Reports to use

  • Verified product identity and specifications sufficient to write the requested fields without inventing characteristics.
  • The requested destination fields and applicable marketplace/category rules; unresolved rules must be marked for review.

Optional inputs

  • Existing listing, packaging, brand style guide and product-family conventions.
  • Dated, product-relevant search-term or SQP evidence and customer questions.
  • Confirmed Item Highlights availability and field schema for the relevant marketplace/category.

Next question

Review the draft against the final product specification and the exact marketplace field rules before a person updates the listing.

Check readiness for a sales event

By the MerchantSpring team

Bring stock, advertising and listing checks into a dated plan for your next sales event.

What you’ll get

  • Event and snapshot details, source status and a module-coverage table.
  • A prioritised preparation list showing deadlines, dependencies, evidence, owner where known and the decision required.
  • Supported stock or economics calculations with assumptions, scenario labels and excluded inputs.
  • A readiness conclusion limited to assessed modules and a short list of the missing data most likely to change the decision.

Your inputs

  • Named event, exact start/end and timezone, marketplace, product scope and current snapshot time.
  • Official event requirements/deadlines or the user's confirmed internal promotion schedule.
  • Available stock, recent demand, inbound dates, advertising, cost and listing data; select only relevant modules.
  • Lead times, safety-stock policy, margin floor and capacity constraints where those assessments are requested.
  • Any explicitly chosen demand/discount scenarios and who owns the resulting decisions.

Reports to use

  • A confirmed event schedule and as-of date/time, or an explicit user-supplied planning assumption clearly labelled as such.
  • At least one usable operational module with its dated inputs: inventory/demand, advertising, product economics, listing readiness or policy/offer eligibility.

Optional inputs

  • Sellable stock, reservations, dated confirmed inbound, receiving lead time and recent daily unit demand.
  • Product costs, relevant fee rules, discounts and advertising assumptions for a contribution scenario with a defined scope.
  • Mature campaign/search-term results, confirmed budgets and the user's performance goals.
  • Actual listing status, product-content review, Featured Offer or deal eligibility evidence and authoritative event deadlines.

Next question

Update this review with confirmed inbound availability and the final event assumptions, then identify which decisions can move forward.

Explore what you can ask through MCP

By the MerchantSpring team

Check the reports available through your MerchantSpring connection and choose a matching workflow.

What you’ll get

  • A compact table of requested report, channel/source, observed status, diagnostic period and evidence.
  • The workflows supported by the observed required fields, with optional modules separated.
  • A short list of remaining checks and the most useful next step.
  • Separate labels for live-connection evidence and supplied-file suitability.

Your inputs

  • Name the channels or accounts, or choose from those listed by the connection.
  • Name the intended questions so the check stays focused.
  • Set a diagnostic reporting period; a small recent complete period is usually sufficient for access checks.
  • If using files instead, supply the relevant reports with source, period, columns and metric definitions.

Reports to use

  • For a connection check: tool descriptions/schemas exposed by the current authenticated assistant connection and responses from limited supported report requests.
  • For a file check: readable reports with enough source, period and field information to assess their suitability.

Optional inputs

  • The user's intended workflows and known account/plan constraints.
  • Documented tool limits, pagination rules and report-generation status definitions.

Next question

Run the most useful workflow supported by the fields you verified, keeping the analysis within the accounts, period and source coverage you checked.

Put your prompts to work

Choose a question, add your channel and dates, and start a conversation with your data.

Inside MerchantSpring

Ask the Insights Agent about your channels, products or campaigns, then follow up on what you find.

In your AI workspace

Bring your MerchantSpring data into an MCP-compatible assistant you already work with.

Claude ChatGPT Cursor Codex Gemini CLI VS Code

For work you repeat

Keep a useful method as a skill in an assistant that supports it, and bring your own question to the next review.

See how this could fit the way your team works.

Book a demo

Prompts and skills, explained

A few answers to help you get started. Want to see what this could look like for your team?

Book a demo
What is the difference between a prompt and a skill?

A prompt starts a conversation with your AI assistant. A skill keeps a method available to reuse in an assistant that supports skills.

Where can I use these prompts?

Try an analysis prompt in the Insights Agent inside MerchantSpring, or use your preferred assistant with MerchantSpring MCP connected.

Can I adapt them to my business?

Yes. Change the channel, products, dates or question to suit the decision you’re working on.

Will you add more prompts and skills?

Yes. We’ll add examples as new features and improvements arrive. If there’s a topic you’d like us to cover, let us know.