Usage
What the vendor sees
Section titled “What the vendor sees”On the product page. Above the images, a meter shows the vendor’s plan, images used, attachments used and the file size limits. Under each description a line such as “Images here: 2 of 5 on your plan” shows the description limit.
At the limit. The meter says “Limit reached.” and names the plan that allows more, with a Compare plans link to the plan page. A vendor employee who cannot open the plan page sees “Ask your account owner to change the plan.” instead of the link. If no available plan gives more, the vendor sees “Contact the marketplace if you need more.”
When something is refused. A notification says what was not added and why, for example:
Images not added: 2. The Starter plan allows 3 images per product. Images already on the product are unchanged. The Growth plan allows 8. Compare plans
On the plan cards. Plans show lines such as “Up to 8 images per product” and “Up to 5 MB per image”.
What is refused
Section titled “What is refused”| Upload | Rule |
|---|---|
| New image | Refused when the product already has the limit. Others in the same save are added until the limit is reached. |
| Replacing an image | Always allowed, it adds nothing. Removing one and adding one in the same save also works at the limit. |
| Image over the size limit | Refused. When it was to replace an image, the old image stays. |
| Image in a description | Images already saved in that field and language stay. A new image is left out if the field is at its limit. The text is saved. |
Very large inline image (data:) in a description |
Counts against the size limit too. |
| New attachment | Refused at the limit or above the size limit. |
| Replacing an attachment file | Refused above the size limit, and the old file stays. |
Background images in inline CSS count as images in a description.
Each product variation is a product of its own and has its own count. Option images are not counted, and neither are the vendor’s logo and other shop images.
Plan downgrades
Section titled “Plan downgrades”Nothing is deleted. A product with 12 images on a plan that allows 8 keeps all 12, online, with all its description images. The vendor can edit it, replace images and remove them, but cannot add. Adding works again once the product is below the limit. The meter explains this on the product page.
REST API
Section titled “REST API”Core lets vendors write products over the REST API only when the core Vendor privileges add-on is active. The same limits apply to a vendor’s API user.
- When creating a product, images over the limit are left out and the product is created. Check the images with a GET.
- When updating images, core deletes the old images before it adds the new ones. So a PUT with
image_pairsormain_pairthat would end above the limit is refused with 403 and nothing changes. The product may keep the count it already has, also above the limit after a downgrade.
GraphQL
Section titled “GraphQL”The vendor mobile app and other GraphQL clients save products through update_product and create_product. Description limits and image limits apply there too: images over the limit are left out and the rest is saved.
GraphQL has no refusal step. A mutation with a new image_pairs list replaces the old list in core before the limits run, so a product above the limit after a downgrade ends at the plan’s limit if the vendor sends a new list that way. Other GraphQL edits leave the images alone.
CSV import
Section titled “CSV import”Descriptions are limited like in the panel. Images over the limit are skipped and the rest of the row is imported. With “Remove additional images” on, a product above its limit keeps its images, because the new ones could not all be added.
Vendors at the limit
Section titled “Vendors at the limit”Vendors > Vendor plan limits > Vendors at the limit lists vendors whose uploads were refused in the last 7, 30, 90 or 365 days, with counts per type. Refused API updates are counted too. Open plan goes to the vendor’s plan. The log keeps one row per vendor, type and day, for one year.