Browntape
Browntape is an aggregator platform that facilitates the flow of inventory and order data from your selling locations (stores). It helps merchants selling on different sales channels to use it as a standalone platform for managing orders and inventory instead of individually managing the data on Flipkart, AJIO, Amazon, etc.
Once you have installed this extension, it will be available in the Extensions section on Fynd Platform.
Inventory
Inventory Summary
- Within the inventory summary, we collect various API calls for inventory in batches.
- Here you can access a comprehensive inventory log along with seller identifier, location code, status, response, total inventory count of products sent to the Fynd Platform by Browntape, and the total inventory count of products accepted by the Fynd Platform from Browntape after incorporating buffer quantities.
The seller identifier and location code in these logs are distinct, ensuring there are no duplicates for these two entities.
- By default, all logs received for a specific company with a unique seller identifier and unique location code are accessible within the tab.
- You can utilize the search boxes located at the top to find logs associated with a particular seller identifier or a specific location code. Input your search criteria, and the relevant logs will be filtered accordingly.
- The listed drop reasons are retrieved directly from the API calls.
Inventory
By default, all logs received for a specific company with a unique seller identifier and unique location code are accessible within the tab.
Use the search boxes at the top to find logs associated with a particular seller identifier or a specific location code. Input your search criteria to filter logs accordingly.
The listed drop reasons are retrieved directly from the API calls.
- Seller Identifier – A unique identifier or code assigned to a specific seller.
- Location Code – A unique identifier or code for a specific selling location.
- Quantity – Live inventory in Fynd Platform.
- Updated on – Orders received on Fynd Platform for an SKU.
The date filter allows you to track inventory updates for up to one year.
Logs
When an API call is made, the acknowledgement or confirmation of the execution is typically sent back in the form of a request ID. This unique identifier helps track and verify the specific log of API calls of a specific batch received and processed by the server.
Payload
Request Body
location_idis the location code.skuis the alphanumeric code assigned to each product for inventory tracking and management.quantityis the quantity of the product for cataloguing.
Detailed Log
In the detailed log, the payload contains all the data mapped for cataloguing purposes. This data is transferred from the Article Database (Article DB), which holds the raw master data, to the Fynd Platform.
Request Body
| Field | Type | Description |
|---|---|---|
store_id | string | The store ID created on the Fynd Platform |
seller_identifier | string | Unique identifier of product (barcode from Article DB) |
total_quantity | integer | Total count of inventory available |
price_effective | float | Effective selling price after discount |
price_marked | float | Maximum retail price of the product |
company_id | string | Unique code of the company |
buffer_message | string | Buffer message if any buffer quantity applied |
trace_id | string | Trace ID to track request batch from Browntape |
store_code | string | Store code on the Fynd Platform (different from store ID) |
raw_quantity | integer | Raw quantity of the products |
Manual Sync
The operation is utilized when there is an issue with inventory synchronization. If inventory sync is successfully received from Browntape but is not reflected in Fynd Platform, you can manually trigger the synchronization to align the two systems in quantity.
Use this functionality after applying buffer so that inventory flows to Fynd Platform after subtracting buffer quantity. Once the sync is completed, the changes will reflect on your opted sales channels. You can sync inventory manually to Fynd Platform by using:
- Seller Identifier: This will sync the inventory for all SKUs or manually selected SKUs present across all selling locations.
- All seller identifiers within a specific date range
- Comma–separated multiple seller identifiers within a specific date range
- Location Code: This will sync the inventory for all SKUs present in these selling locations.
- All active location codes within a specific date range
- Comma–separated multiple location codes within a specific date range
Inventory Timeline
- Enter a seller identifier in the search box, select the location code, select the status of the API call, and enter a date range.
- Click Get Logs to view the status of inventory updates of a product for up to a month.
- This tab lets you know whether an article’s inventory push was successful or not.
- Failure reasons could include: article not available, store mapping not found, duplicate batch record discovered, SKU missing for a store, location not available, and so on.
Inventory Statistics
- The total inventory count of products from the master catalog entries accessed in the article DB is mirrored in the received inventory.
- The total inventory count of products synced on the Fynd Platform from the article database.
- The percentage drop represents the decrease in the inventory count, showing the difference between the received inventory and the consumed inventory.
Drop Reasons
The drop percentage is attributed to specific reasons, which are detailed in the drop reason section. There are four main reasons for inventory consumption decrease from the Article Database to the Fynd Platform:
- Location mapping not found
- Store not found
- Seller identifier not found
- Buffer
These reasons are visually represented and specified in the form of a pie chart, making it easy to grasp the distribution of inventory drops due to each of these factors.
.png)