Prepare a Black Friday campaign across the shop

Paid versionCommerceReady job: Get ready for Black Friday

Black Friday is set up days ahead in one conversation, not at 2 a.m. the night before.

What it replaces: 1-2 days of campaign setup

What you write to Claude

„Black Friday plan: -20% on top 30 sellers from last year, code BF26 for 10% on everything else, homepage banner, and category intros mentioning the sale. Dates 2026-11-27 to 2026-11-30. Prepare everything, I approve step by step.”

The problem

Black Friday is the busiest week of the year and every year we set it up at 2 a.m. the night before.

What Claude does

  1. Claude finds last year's best sellers and prepares the discount on them with dates.
  2. It prepares the discount code, which starts switched off.
  3. It writes short category texts about the sale.
  4. You approve each part separately, and after the weekend everything can be undone together.

What you get

The whole campaign is prepared in one conversation, approved part by part, with a clean way back.

You stay in control

You see every change before it is saved, nothing happens without your yes, and you can undo it later. Prices, discounts and stock stay switched off until you turn them on, and unusually large changes need an extra confirmation.

See pricing

Related use cases

For developers
Area
2 · Commerce
Connector
daily connector
In the free Audit
no, paid version only
For
Marketer / SEO, Agency / freelancer
Tools
ps_get_product_sales, ps_manage_specific_prices, ps_manage_cart_rules, ps_update_category_content, ps_list_changes, ps_revert_change, ps_get_ready_job, ps_manage_catalog_price_rules

Step by step

  1. Finds last year's top 30 sellers with ps_get_product_sales.
  2. Prepares -20% on them with ps_manage_specific_prices (for whole categories or brands, one ps_manage_catalog_price_rules rule is simpler) (action add, 2026-11-27 to 2026-11-30) and shows the preview.
  3. Prepares the BF26 code with ps_manage_cart_rules (action create, inactive) and activates it after a separate approval.
  4. Drafts category intros mentioning the sale with ps_update_category_content, each with its own preview.
  5. Leaves the homepage banner to the service connector (block 3), where theme files are edited, and lists every change with ps_list_changes so the whole campaign can be reverted after the weekend.

Safety

Commerce (block 2) runs on the daily connector, is off after installation and has its own switch. Claude acts as the connector's PrestaShop employee, so the action must also be allowed in that employee's profile. Every write shows a preview, runs only after your approval (single-use token valid 30 minutes, blocked if the data changed in the back office in the meantime), is logged in the change history and can be undone with ps_revert_change. The voucher code is created inactive, and the -20% stays below the 50% warning threshold. Sales data comes without customer data.

Last updated: 2026-10-05