Weekly Amazon FBA returns root cause review with Linear tickets and Slack digest

Build me an agent workflow that runs every Monday at 7am local time and produces a weekly Amazon FBA returns root cause review. I want it to take last week's customer returns, group them by SKU, file a Linear ticket for every problem SKU, and post a single digest to Slack.

Trigger: cron, every Monday at 7am.

Step 1. Use the Amazon Seller Partner Create Report operation to request a GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA report for the prior 7 days (Monday through Sunday). At the same time, request a GET_SALES_AND_TRAFFIC_REPORT for the same period so we know units sold per SKU.

Step 2. Poll the Get Report operation for each report until status is DONE. Once each is DONE, use Get Report Document to download the data.

Step 3. Parse the returns file. For each returned unit, categorize the buyer reason into one of these buckets: defective or damaged, did not match description, wrong size or fit, ordered by mistake, no longer needed, other. Aggregate by SKU and ASIN. Capture any free-text customer comments verbatim.

Step 4. Compute a return rate per SKU using the units sold from the sales and traffic report (returns / units sold for the same 7-day window). Compute each bucket's share of that SKU's returns. Compare to last week's return rate for the same SKU and store the trend (up, down, flat).

Step 5. Flag a SKU if either of these is true: return rate above 5%, OR defective-or-damaged share above 40% of that SKU's returns. Both thresholds should be obvious config values at the top of the workflow so the operator can tune them.

Step 6. For each flagged SKU, use Linear's Create Issue operation to file a ticket in a configured product team. Title: 'FBA returns review: <SKU> (<return rate>%)'. Description in Markdown: SKU, ASIN, marketplace, return rate this week vs last week (trend arrow), top reasons broken down by share, and three representative verbatim customer comments. Set priority to High (priority = 2) when the defective-or-damaged bucket is the dominant reason, otherwise Normal (priority = 3).

Step 7. Use the Slack Bot Send a Message operation to post one digest in a configured channel. The digest should list every Linear issue created with deep links, the aggregate return rate for the period, and the three SKUs to watch next week (the ones closest to breaching the threshold but not over it yet).

Edge case: if no SKU breaches the thresholds, skip Linear entirely and post a short clean-week note in Slack instead with the aggregate return rate and the three SKUs to watch.

Configurable inputs to surface at the top of the workflow: the Amazon marketplace IDs to include, the Linear team to file tickets in, the Slack channel to post the digest in, the return rate threshold (default 5%), and the defective share threshold (default 40%).

Additional information

What does this prompt do?

Pulls last week's Amazon FBA customer returns and pairs them with units sold so every reason is sized as a return rate, not a raw count.
Sorts the reasons your buyers gave into clear buckets like defective or damaged, wrong size or fit, did not match description, and ordered by mistake.
Files a Linear ticket for each problem SKU with the trend, the top return reasons by share, and three real customer comments so your product team can act on it.
Posts one Slack digest with deep links to every ticket created, the overall return rate for the week, and the three SKUs to watch next week.
Skips ticket creation entirely on clean weeks and posts a quiet good news note in Slack instead.

What do I need to use this?

An Amazon Seller Central account with access to FBA reports.
A Linear workspace and the team you want product tickets filed in.
A Slack workspace and the channel that should receive the Monday digest.

How can I customize it?

Change the schedule. Mondays at 7am is the default, but any weekly time works.
Tune the thresholds. The defaults flag any SKU above a 5% return rate or with more than 40% of returns marked defective or damaged.
Pick the Linear team and the Slack channel that should receive output, and decide which marketplaces (US, EU, etc.) to include.

Frequently asked questions

Does this work for sellers outside the US?

Yes. Amazon's returns report is available in every marketplace region. You can run it for North America, Europe, or the Far East, and you can scope it to specific marketplaces like UK or Germany if you only want to review certain regions.

What counts as a problem SKU?

By default, any SKU with a return rate above 5% for the week, or any SKU where more than 40% of its returns are flagged defective or damaged. Both numbers are easy to change in the prompt before you save the workflow.

Will it spam Linear with duplicate tickets every week?

Each Monday's run is treated as its own weekly review, so a SKU that breaches the threshold two weeks in a row will get a fresh ticket. You can ask your product team to close the previous one, or add a note to the prompt to skip SKUs that already have an open ticket.

What happens on a quiet week?

If no SKU crosses the thresholds, the workflow skips Linear completely and posts a short clean week message in Slack so the channel still hears from it.

Where do the customer comments in the Linear ticket come from?

Amazon's FBA customer returns report includes the buyer's reason and an optional free-text comment. The workflow picks three representative comments per flagged SKU and pastes them verbatim into the ticket so the product team sees the actual customer voice.