Store Inventory & Pricing Feed

Feed Specification

The store inventory feed is used for the Find-In-Store feature. On the PDP, a user can opt to see if a product is available in a nearby store.

Frequency

• Full Feed - Once a month.
• Delta Feed - Once a day to update positions based on prior day transactions.

Note The manual upload or scheduled upload feature has an input text field for "Column Names" for providing field names in the column order of the feed file. You must only provide the column names in one way, either in the feed file itself or in the text field. If the column names are provided both in the text field and in the feed file, the column names in the feed file will get indexed.

Note All feed files should be saved in a UTF-8 (not to be confused with UTF-8 with BOM) format else you receive an error during upload.

Content

CMS Field Display Name	Mandatory	Description	Data Type	Example Data
product_id	Yes	The identifier of the item/product.	Number	123
quantity	Yes	The available quantity in the store.	Number	1000
store_id	Yes	The ID of the store where the item is located.	Number	234
store_price	No	The store-specific price of the product. This is the primary price that is used for in-store transactions for the current store in the POS app.	Number	15.99
list_price	No	The manufacturer's suggested retail price (MSRP). Note If this value is present in this feed it will overwrite the list price provided in the product feed.	Number	21.99
sales_price	No	The price of the product that is not store-specific. To utilize this field, the list_price field is required. Once both are present this value will overwrite the sales prices in the product feed.	Number	14.99
allocated_quantity	No	The number of items that are allocated towards store fulfillment orders. This will reduce from the availability.	Number	1
clearance_instruction_texts	No	The multiple pipe-delimited instructions for clearance items. The ordering must match items in the serial_numbers field.	String	display|display
floor_demo_quantity	No	The number of items that are on display for product demonstration. This will reduce from the availability.	Number	7
not_for_sale_quantity	No	The number of items that are not for sale. Not for sale quantity will be picked up by any adjustment made. This will reduce from the availability.	Number	5
product_locations_within_store	No	The multiple pipe-delimited locations of clearance items. The ordering must match items in the serial_numbers field.	String	Aisle1B|Aisle1B
quantity_in_transit	No	The number of items that are in transit to the store.	Number	3
quantity_on_hand	No	The physical number of items at a store.	Number	1000
quantity_on_order	No	The number of items that are part of a purchase order.	Number	4
returned_items_quantity	No	The number of items that have been returned at the store. Return to vendor quantity will be picked up by any transfers made. This will reduce from the availability.	Number	6
safety_stock_quantity	No	The number of safety stock item, which will reduce from the availability.	Number	2
serial_number_based_prices	No	The multiple pipe-delimited discounted prices of clearance items. The ordering must match items in the serial_numbers field.	String	129.00|139.00
serial_numbers	No	The multiple pipe-delimited serial numbers of the specific product variants that can be sold as clearance items.	String	100347721|100347722
store_banner	No	The store banner text on the app.	String	Welcome to the store
store_promo_text	No	The store-specific promotion text.	String	On sale now

Note When running a Store Inventory Delta file, price and inventory are independent of each other. This means that when the price is sent in the file the inventory is not updated. Conversely, when the inventory is sent in the file then the price is not updated.

Store Price vs Sale Price Settings

There are two settings in CMS that can alter the behavior of the POS app when it comes to the pricing of a product:

• Enrich store pricing to product (storePricing) (Store Management | Store Settings | Search).
• Store price overrides Sale price (Store Management | Store Settings | Search).

Remove Store-Level Pricing for Specific Stores

If store-level pricing is configured for multiple stores, but you need to remove it for a specific store while keeping it for others, here’s how you can do it:

Example scenario:

• Stores A, B, and C have store-level pricing configured
• You want to remove store-level pricing for Store A and revert it to catalog pricing, while keeping store-level pricing for Stores B and C intact.

Steps to Remove Store-Level Pricing for Store A:

1. Use the Full Store Inventory Feed:
   • Exclude Store A from the full feed
   • This will delete all store-level pricing for Store A, reverting it to catalog pricing

2. Use the Delta Store Inventory Feed:

   • Update the Delta Feed for Store A
   • Include catalog prices in the update to overwrite the existing store-level pricing for Store A

Known Issues & Restrictions

When using this feed, consider:

• Uploading a store inventory full or delta file doesn't update the Inventory Ledger.
• If you see a 504 error while uploading a file, it may indicate that it is too large (e.g., 10mb). Try downsizing your file and upload again.
• In the initial file upload, the required Target Fields (denoted by an asterisk) must be mapped so they can be available as columns. However, they don’t need to have values and just need to line up with the schema.
• If a StorePrice is provided in this feed then there are three prices in the POS app:
  • ListPrice (MSRP) - Provided in Product Feed.
  • SalePrice (Discounted price) - Provided in Product Feed.
  • StorePrice (Store level pricing) - Provided in Store Inventory Feed. By default, the lower sale price and store price are offered to the customer as the price of an item. If a brand wants to change this behavior to use store price as the base for store-level pricing (even though higher than the sale price) then the store setting of StorePrice override can be configured to exhibit this behavior.