One approved master, many marketplace outputs
Create channel derivatives without turning Amazon, eBay or Shopify requirements into separate editing projects.
Reading time10 minute guide
Written forMarketplace managers and ecommerce content teams
FormatOperating guide and checklist
Updated20 August 2026
Approve product truth first
Colour, edges, texture, included components and hero view belong to the product standard. Channel crop, dimensions and compression come after that standard is approved.
Retain a reusable master
Keep a high-resolution colour-managed master with enough canvas and, where useful, transparency. Do not derive a new channel image from another compressed derivative.
Store channel rules as profiles
Each profile records canvas, background, crop, format, colour space, naming and delivery folder. Add an owner and review date because platform rules change.
Validate after publication
Use marketplace diagnostics and live-page review to refine the profile. No editing provider can guarantee acceptance independently of listing data and account policy.
Questions teams ask before production.
01Can one file serve every marketplace?＋
Sometimes, but channel layout and compression differences usually justify controlled derivatives.
02Should marketplace rules be hard-coded forever?＋
No. Store them as reviewable profiles and confirm them at delivery time.
03Can Rupato publish directly?＋
Only after each company authorises and tests the relevant marketplace connection.
ONE ORDER OR A COMPLETE CATALOGUE
Make the brief clear before the first file moves.
Rupato keeps uploads, specifications, tasks, review and delivery attached to the same production record.
Start an order ↗