We use a SaS system to support the Catch Marketplace.
This means the APIs that we have available are not only straightforward to work with, but are a standardized set-up.
Being standardized, means there are a set of standard offer fields (e.g. price, qty, sku etc). But within our system, we can define further fields if specifically required for our Marketplace.
It is important to understand these custom fields, as some may be mandatory.
You can call AF01 to learn all of our custom values/codes.
We have three fields custom within the Catch offer data:
When calling the API, these fields need to be included within the offer_additional_fields sector.
</offer> <offer> <logistic-class>Logistic code(this must match your account set-up) </logistic
-class> <price>Your RRP price</price> <product-id>YOUR SKU</product-id> <product-id-type>SHOP_SKU</pro duct-id-type> <quantity>999</quantity> <sku>YOUR SKU</sku> <discount-start-date>YOU CAN LEAVE THIS FIELD BLANK</discount-start-date> <discount-price>Your sell price</discount- price> <state>11 (This value refers to a 'New' product) </state> <update-delete>UPDATE</update- delete> <offer-additional-fields> <offer-additional-field> <code>club-catch-eligible</cod e> <value> Accept: TRUE/FALSE Learn more about this field here</value> </offer-additional-field> <offer-additional-field> <code>tax-au</code> <value>ACCEPT: 0/10 Learn more about this field here</value> </offer-additional-field> </offer-additional-fields>
<value> Accept: NUMERIC VALUE (e.g. 2)</value>
</offer-additional-fields> </offer> <offer>
When uploading via a spreadsheet, such as .csv or XLSX, the same field names will be used with no mention of offer-additional-field - this only for XML/JSON format.