Overview
This FAQ answers common questions about delivering and maintaining Product Feeds, including update frequency, stock handling, localization, and required attributes.
How frequently should the file be provided?
The product feed should be updated at least daily. More frequent updates on stock levels are encouraged.
Can we upload to your (S)FTP server?
Mapp does not operate an FTP server. Instead, S3 access is provided for feed delivery.
Should out-of-stock items be included?
Generally, items should only be removed from the feed if customers can no longer access them.
If an item is available in only some sizes, the feed should continue to list all sizes. This allows Mapp to distinguish between:
A size that is temporarily out of stock
A size that was never produced
Do you require attributes such as style, fit, or similar?
These attributes are assigned by Mapp’s styling team and automated processes. However, if you already have this information available, including it in the feed is helpful.
Is it possible to update stock levels more frequently?
Yes. If more frequent updates are required, you can provide a separate stock feed, either full or incremental.
The stock feed must be a CSV file with the following columns:
Field | Description |
|---|---|
| Identifier for the size- and color-specific product variant |
| Either a numerical quantity or one of the following statuses: |
Can you support multiple locales?
Yes. XML-based feeds are recommended when working with multiple locales, as other formats can become very wide.
You can add a locale attribute to relevant fields, for example:
<Name locale="...">Green Jumper</Name>
<Name locale="fr">Pull Vert</Name>Our images follow a systematic naming convention. Do we need to provide all image URLs?
Please provide image URLs wherever possible. If this is not feasible, contact Mapp to discuss alternatives.
Any product attribute that should be displayed or returned in API responses must be included in the feed, including alternate image URLs.