Skip to content

Supplier stock sync with read back check

A daily job pulls product and stock data from suppliers, writes it to the store and reads every write back to verify it. Anything that cannot prove it worked fails loudly instead of reporting success.

Ecommerce and resaleWorks with Claude Code · Cursor+1Community example
Build your promptSee requirements

What it does

  • Pulls product and stock data from each supplier
  • Writes updates to the store, then reads them back and compares
  • Never overwrites fields you corrected by hand
  • Rebuilds the shopping feed with one offer per product per market
  • Stops the run with a clear error if a write cannot be verified

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Any fix after a failed run
  • Publishing anything public, like a social post
  • Changes to pipeline code, which go through a pull request

You decide what happens next.

More about this workflow

This setup is for online sellers and resale shops juggling listings, orders and buyers. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it pulls product and stock data from each supplier. Next, it writes updates to the store, then reads them back and compares. Then it never overwrites fields you corrected by hand. After that, it rebuilds the shopping feed with one offer per product per market. Finally, it stops the run with a clear error if a write cannot be verified. It works with your store admin, CI and git host, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before any fix after a failed run, publishing anything public, like a social post and changes to pipeline code, which go through a pull request, and says plainly if a step cannot be undone.

“every write is verified and every irreversible step passes a human approval gate”
drostark drostark on GitHub · Oct 13, 2026
Before you startStore admin · CI accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • Shopify

    Handles the store admin part of this job. Grant read orders and products.

    API required: Yes. Needs a Shopify app with an access token and the admin scopes you approve.

    Sign up: Shopify

  • GitHub

    Handles the ci and git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Gemini 3.8 Flash

Built for agent workflows, with a free tier to test on.

$0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026. $1.50 and $7.50 from January 1, 2027.

Google docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for many listings at once.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

ones you edit by hand

2Your prompt

4 of 4 still empty
Fill these in before you run it: [SUPPLIER FEEDS] [STORE] [MARKETS AND LANGUAGES] [PROTECTED FIELDS: ones you edit by hand] You are the Supplier stock sync with read back check agent. A daily job pulls product and stock data from suppliers, writes it to the store and reads every write back to verify it. Anything that cannot prove it worked fails loudly instead of reporting success. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Pulls product and stock data from each supplier - Writes updates to the store, then reads them back and compares - Never overwrites fields you corrected by hand - Rebuilds the shopping feed with one offer per product per market - Stops the run with a clear error if a write cannot be verified What you must never do without a yes from a person: - Any fix after a failed run - Publishing anything public, like a social post - Changes to pipeline code, which go through a pull request Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor, OpenAI Agents SDK

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Shopify with its own login, not yours. Grant read orders and products.
  2. 2Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: any fix after a failed run, publishing anything public, like a social post, changes to pipeline code, which go through a pull request.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Supplier stock sync with read back check](https://trustcase.dev/badge/supplier-stock-sync-with-read-back-check.svg)](https://trustcase.dev/use-cases/supplier-stock-sync-with-read-back-check)
HTML
<a href="https://trustcase.dev/use-cases/supplier-stock-sync-with-read-back-check"><img src="https://trustcase.dev/badge/supplier-stock-sync-with-read-back-check.svg" alt="Trustcase trust score for Supplier stock sync with read back check" height="20"></a>

More ecommerce and resale workflows