SOURCE DATAAn ERP MCP connector reads authorized SKU, variant, cost, stock, dimensions, packaging, logistics and existing Listing fields. Amazon SP-API provides the marketplace's current Listing state. SellerSprite supplies third-party keyword, rank and competitor trends; public or authorized high-performing content is used only to study composition, setting and pacing. Conflicting fields stop for review.
MODEL PARAMETERSEach SKU sends source product images plus structured JSON. product_truth locks the SKU and variant, colour, material, dimensions, packaging, logo, set quantity, allowed claims and forbidden changes. style_reference carries only visual direction. Task fields specify platform, language, aspect ratio, output count and whether to validate, save as a draft or wait for release.
BATCH IMAGE CONTROLFiles stay tied to SKU, variant and channel from generation onward. A vision model runs the first check against the source images for shape, colour, logo, packaging text, set quantity and use. Clear failures are regenerated; low-confidence, OCR-disputed and high-risk results go to human review before entering the upload queue.
PLATFORM WRITE-BACKShopify CLI or a custom CLI calls the authorized Admin GraphQL API to create or update an unpublished product, upload and order media, write alt text and bind variants. A single Amazon SKU can be pre-validated through Listings Items API; batches use JSON_LISTINGS_FEED, with image URLs submitted as Listing attributes. A person confirms the final write and public release.
RESULT READ-BACKThe system stores the relevant SKU or ASIN, Shopify product and file IDs, Amazon feedId, processing state and errors. It then checks Amazon Listing issues and feed reports, and waits for Shopify media to be READY before checking variant binding and channel visibility. Only the requested state closes the task; ACCEPTED or DONE alone does not prove that a product is live or searchable.