A useful question. A clear next step.

All templates ask for read-only requests. Check the connection, date range and results in your chat. A prompt does not replace technical access controls; available data depends on the marketplace and your permissions.

12 of 12 prompts

There is no prompt for this combination yet.

Check OTTO SKU [SKU] in [connection] using read-only requests.
Show its marketplace status, active, MOIN, error code and original message, hints, lastModified and any shop link.
Separate errors from optimisation hints. State the source and retrieval time. Missing fields or records are unknown; do not infer a status.
Explain what is evidenced, what remains open and what I should check next. Do not change products or activation settings.

Read all available OTTO quantities in [connection], following every results page. My minimum stock threshold is [quantity] units.
Show SKUs with quantity below this threshold, sorted by quantity ascending: sku, quantity, lastModified. Identify zero quantities separately.
State the source, retrieval time and completeness. An unknown SKU or missing value is not zero. lastModified is not the retrieval time and does not prove a synchronisation failure.
Describe these as reported OTTO quantities, not verified warehouse stock. Use read-only requests only.

Create a read-only shipping worklist for OTTO [connection]. Query fulfillmentStatus=PROCESSABLE with mode=AT_LEAST_ONE and no lower date limit. Follow all nextcursor pages.
Keep only PROCESSABLE items and count each salesOrderId plus positionItemId once. Show the 20 oldest by processableDate, with order ID, item ID, SKU and expectedDeliveryDate where supplied.
Show the total and number of omitted items. List missing dates separately; do not infer a shipping deadline from expectedDeliveryDate. State source, retrieval time and completeness. Do not output buyer details or mark anything as shipped.

Check OTTO Ads in [connection] read-only for [start date] to [end date] in CET/CEST. State the precise boundaries and supply both dates. My target ROAS is [target].
Read all campaign pages. Show each campaign's ID, name, status, totalCosts, totalSales, ROAS, dateRange and lastCalculatedAt. Check monetary units in the current schema and normalise to euros.
Recalculate ROAS when costs are positive. Sort campaigns below target by costs descending. List missing data and zero-cost cases separately as not assessable. ROAS is not profit. State retrieval time and completeness. Do not change budgets or campaigns.

Read my Kaufland offers in [connection], storefront [country code], fulfillment_type [fulfilment type], following all limit/offset pages.
Show offers with amount=0: id_unit, id_offer, id_product, amount, status and is_live where supplied. List missing quantities separately; missing is not zero. Put positive quantities with is_live=false in a separate review list.
State source, retrieval time, filters, total count and completeness. Newly created offers may appear with a delay. Do not infer visibility or physical warehouse stock from quantity or status alone. Do not change anything.

Check the regular Kaufland Buybox read-only for [EAN or id_product], storefront [country code], condition [condition], in [connection]. My id_offer is [reference]. Resolve an EAN to its product ID first and confirm the title.
Show up to ten available offers with reported rank, seller, condition, item price, shipping costs, combined price, delivery range and fulfilment type. Verify units before converting values. Calculate combined prices only from confirmed item and shipping costs; missing shipping costs are not zero.
Identify my offer only with a confirmed match. State retrieval time, returned offer count and num_units. Separate observations from possible explanations. Do not promise a rank improvement or change prices.

Analyse Kaufland [connection], storefront [country code], fulfillment_type [fulfilment type], read-only. Use creation time from [start date] 00:00 inclusive to [end date] 00:00 exclusive, Europe/Berlin.
Read all order-unit pages and all statuses. Count each id_order_unit once. Group only by confirmed SKU mapping and condition.
Show ordered units, cancelled units, units excluding cancellations and cancellation share. Calculate shares only with a positive denominator. Separate unknown statuses and mapping gaps; affected rankings remain provisional. Returns are not additionally deducted. State filters, retrieval time and completeness. No buyer details, revenue or profit estimates, or changes.

Check Kaufland [connection], storefront [country code], fulfillment_type [fulfilment type], read-only.
Read return-units with need_to_be_returned, return_arrived, return_in_clarification and return_in_repair, with no lower date limit and across all pages. Count each id_return_unit once.
Add the return-level status for each id_return. Show item ID, return ID, item status, return status and creation date. Group by processing status, oldest first. Suggest next checks without inferring a binding deadline from age.
State source, retrieval time and gaps. No customer or address details or free-text notes. Do not change anything or send messages.

Read all offer pages using OF21 in [Mirakl connection] and [shop], read-only and respecting request limits. My stock threshold is [quantity].
Show offer_id, shop_sku, product_sku, quantity, active and any returned inactivity_reasons. Separate quantities below the threshold, quantity=0 and inactive offers with positive quantities. List missing values separately.
Do not infer activation status from state_code. If an existing OF26 check returns zero, this does not establish whether quantity is zero or the offer is unavailable.
State source, shop, retrieval time and completeness. These values do not prove physical warehouse stock. Do not change offers.

Check known product import [import ID] on [Mirakl connection, shop] read-only.
Show import_status, reason_status, creation time, transformation counters, available integration details and report availability. State if processing is still running.
Review available transformation and integration error reports. Group by stage, field and original message; show message counts separately from distinct affected products. Include product references, evidence locations and next checks. Do not invent error codes or required fields.
Missing or unreadable reports do not prove success. State retrieval time and gaps. Do not start an import or change data.

Check [Mirakl connection] and [shop] read-only. Read WAITING_ACCEPTANCE and SHIPPING separately using order_state_codes, with no lower date limit, across all pages and respecting request limits.
Count each order_id once per connection and shop, and each order_line_id once within it. Show order and line status separately, offer_sku, created_date and shipping_deadline where supplied.
Sort SHIPPING by available shipping_deadline; list missing deadlines separately. Sort WAITING_ACCEPTANCE by creation date without inferring an acceptance deadline.
State source, retrieval window and completeness. No buyer details. Do not accept orders, confirm shipping or send messages.

Compare reported quantities read-only in [connections and storefronts/shops] using this confirmed mapping: [internal SKU, channel SKU/offer ID, variation, pack size, condition].
Read all required pages. Show channel quantities, status or availability, sources and retrieval times side by side for each product. Separate missing records, missing quantities, zero and inactive offers.
Flag quantity differences for review. Do not add channel quantities into total stock; several offers may share one warehouse pool. Do not infer synchronisation failures from differences alone.
List unresolved mappings separately. State completeness and retrieval time differences. Do not change stock quantities.