Catalog name created for Walmart
\*May vary from brand to brand
| Walmart | Automatically created. | Required (should not be changed) | | **Channel Type** |Channel Type
\*All sales channel types are available as a dropdown in Omnitron.
| Sales Channel | Automatically created. | Required (should not be changed) | | **Status** | The sales channel will not function until it is activated. | Inactive | Default is set to inactive (it needs to be activated). | Required | | **Schema Type** |The information to be stored in the sales channel settings is defined here. Based on the details provided, the necessary information for the sales channel's operation is brought as a form in Omnitron. A schema containing the minimum requirements for the channel's operation is automatically created. Additionally, you can add any other information you want to store here (e.g., data needed for ERP integration of the sales channel). The key-value pairs to be included in the Channel Config are listed here. The dictionary in the value section includes key, label, required, and data\_type.
key -> Information on which key will be used to access the data within the channel config.
label -> Information on how the data will appear in the form in the Omnitron Sales Channel settings interface.
required -> Indicates whether the related value is mandatory or not (true/false).
data\_type -> Specifies the data type of the related value (list, text, integer, bool, json).
|{
"ApiKey": {
"key": "ApiKey",
"label": "Api Key",
"required": true,
"data\_type": "text"
},
"base\_url": {
"key": "base\_url",
"label": "Base Url",
"required": true,
"data\_type": "text"
},
"erp\_code": {
"key": "erp\_code",
"label": "Erp Code",
"required": false,
"data\_type": "text"
},
"SecretKey": {
"key": "SecretKey",
"label": "Secret Key",
"required": true,
"data\_type": "text"
}
}
| The information has been automatically filled with default values. | Required (Additions can be made, but existing fields should not be changed). | | **Base Url** | API URL for Walmart |\[
"Animal",
"Art & Craft",
"Baby",
"Carriers & Accessories",
"Cleaning, Safety, & Other",
"Clothing",
"Electronics",
"Food & Beverage",
"Footwear",
"Furniture",
"Garden & Patio",
"Health & Beauty",
"Home",
"Jewelry",
"Media",
"Musical Instrument",
"Occasion & Seasonal",
"Office",
"Photography",
"Sport & Recreation",
"Tools & Hardware",
"Toys",
"Vehicle",
"Watches"
]
| It is left blank by default. (This information is obtained from Walmart). | Required | | **Feature Flags** | It allows the activation or deactivation of active processes. The important point to note here is that even if the related process is not running, it must still be added here as false. (Detailed information about feature flags is provided in Section 9 under the "Feature Flags" heading below). |{
"get\_orders": false,
"send\_product": false,
"get\_cancel\_orders": false,
"get\_refund\_orders": false,
"send\_update\_orders": false,
"send\_delete\_products": false,
"get\_updated\_order\_items": false,
"send\_updated\_product\_price": false,
"send\_updated\_product\_stock": false
}
| By default, all flags are set to false. | Required | | **Erp Code** | The sales channel code defined for Walmart in the brand. | Walmart | It is left blank by default. | Optional | | **Cancellation Reason Id** | This is the information regarding the cancellation reason that will be written to Omnitron when canceled orders are pulled from Walmart. (The ID information can be retrieved using the endpoint: {omnitron\_url}/api/v1/channel/{channel\_id}/cancellation\_reasons/?cancellation\_type=cancel\&is\_active=true) | 4 | It is left blank by default. | Required | | **Cancellation Mapping** | The cancellation reason from Walmart is mapped to the cancellation reason in Omnitron. Here, the key is the reason ID from Walmart (which can be found in the cancellationReason section of the[ cancelOrderLines API](https://developer.walmart.com/api/us/mp/orders#operation/cancelOrderLines)), and the value is the reason ID from Omnitron. The ID information can be retrieved using the endpoint: {omnitron\_url}/api/v1/channel/{channel\_id}/cancellation\_reasons/?cancellation\_type=cancel\&is\_active=true. |{
“CUSTOMER\_REQUESTED\_SELLER\_TO\_CANCEL”:7 ,
“SELLER\_CANCEL\_PRICING\_ERROR”:5
}
| It is left blank by default. (When left empty, the cancellation process will be carried out using the "Cancellation Reason Id" from the previous step when cancellation information is retrieved from Walmart.) | Optional | | **Refund Reason Id** | If the reason ID in the return data retrieved from Walmart is not found in the Refund Reason Mapping, the refund data will be retrieved using the Omnitron refund reason ID entered in this section and written to Omnitron. (The ID information can be retrieved using the endpoint: {omnitron\_url}/api/v1/channel/{channel\_id}/cancellation\_reasons/?cancellation\_type=refund\&is\_active=true). | 5 | It is left blank by default. | Required | | **Refund Reason Mapping** | The return reason from Walmart is mapped to the return reason in Omnitron. Here, the key is the reason ID from Walmart (which can be found in the refundReason field within the refundCharges section of the[ refundOrderLines API](https://developer.walmart.com/api/us/mp/orders#operation/refundOrderLines)), and the value is the reason ID from Omnitron. The ID information can be retrieved using the endpoint: {omnitron\_url}/api/v1/channel/{channel\_id}/cancellation\_reasons/?cancellation\_type=refund\&is\_active=true. |{
“BillingError”: 7 ,
“Others”: 5
}
| It is left empty by default. (When left empty, the return reasons will be written to Omnitron using the "Refund Reason Id" from the previous step when return information is retrieved from Walmart.) | Optional | | **Failed Integration** | Records with errors during the integration process are temporarily held with a penalty. (Detailed information is provided in Section 3 under the "Failed Integration Settings" heading below). | Check Section 3 for default and example settings | It is filled with default values. | Required | | **Use Cargo Label** | If the brand does not manage the shipping processes (i.e., send\_shipping\_info is not active), and a shipping label is desired to be created when the relevant order is pulled from Walmart, this setting should be activated. | Inactive | It is left blank by default. | Optional | | **Carrier Short Name** | If the brand does not manage the shipping processes (i.e., send\_shipping\_info is not active), and a shipping label is desired to be created when the relevant order is pulled from Walmart, the carrier name information that should appear on the shipping label should be entered here. (This information can be found under the shortName field within[ getCarriers API](https://developer.walmart.com/api/us/mp/sww#operation/getCarriers)). | FedEx | It is left blank by default. | Optional | | **Carrier Service Type** | If the brand does not manage the shipping processes (i.e., send\_shipping\_info is not active), and a shipping label is being created when the relevant order is pulled from Walmart, this is the carrier service information that will be sent to Walmart. (This information can be found under the data>estimates>name section in the[ getShippingEstimate API](https://developer.walmart.com/api/us/mp/sww#operation/getShippingEstimate)). | FEDEX\_2\_DAY | It is left blank by default. | Optional | | **Cargo Label Extension** | If the brand does not manage the shipping processes (i.e., send\_shipping\_info is not active), and a shipping label is to be created when the relevant order is pulled from Walmart, this is the file extension information to be set. (Possible values: application/pdf - image/png) | application/pdf | It is left blank by default. | Optional | | **Channel Store Code** | It is the store code information to be sent to the ERP. | 4042 | It is left blank by default. | Optional | | **Cargo Company Mapping** | When an order is pulled, it ensures that the order is written to Omnitron with a default shipping carrier. Additionally, if the brand does not manage the shipping processes (i.e., send\_shipping\_info is not active) and a shipping label is to be created, the carrier name received in the shipping label creation response is checked to see if there is a corresponding entry. If a match is found, the shipping information is updated accordingly. |{ "default": "3",
“FedEx”: “2”
}
| It is filled with the default key by default. | Required | | **Send Shipping Info** | This setting determines whether the shipping process will be managed by Walmart or the brand. | Inactive | It is left inactive by default. (If inactive or not selected, Walmart will manage the shipping process. If active, the brand will manage the shipping process.) | Optional | | **Shipping Company Mapping** | If the brand manages the shipping processes (i.e., send\_shipping\_info is active), this setting is used to map the shipping company slug from Omnitron (Omnitron -> Settings -> Shipping Companies -> Shipping Company Title) with the carrier information from Walmart (which can be found in the carrier field within the[ orderShipment API](https://developer.walmart.com/api/us/mp/orders#operation/shippingUpdates) under orderLines.orderLine.orderLineStatuses.orderLineStatus.trackingInfo.carrierName.carrier). |{
“Ups”: “UPS”,
“Fedex”:”FedEx”
}
| It is left blank by default. | Optional | | **Attribute Set Strategy** | It is a strategic setting that determines which attribute set the products belong to. | CategoryNode | It is filled by default. | Required (Should not be changed). | | **Use Channel Id In Address Mapping** | If the brand wishes, they can activate this field to perform address mapping on a channel basis. When this field is activated, the channel ID information is added before the address data during the mapping process. During search operations, the sales channel filter is used with the channelId\_address information for querying. | Inactive | It is left blank by default. | Optional | | **Buffer Stock** | This is the value to be deducted from the product's current stock when performing stock feed to Walmart. If no value is entered, the product's current stock will be sent to Walmart. | 3 | It is left blank by default. | Optional | ### 2.1 Flows that run automatically after channel settings are saved When certain fields in the channel settings are saved or updated, a sequence of maintenance flows is automatically queued. These flows prepare the channel for correct product and attribute operations. Manual triggering is NOT required (visible on the Monitoring / Logs screen). **When Category Ids are added or changed** (the `Category Ids` field in the channel config): 1. **Category Node** – Fetches the full category tree for each newly added root category. 2. **Category Attributes** – Fetches attribute definitions belonging to the fetched categories. 3. **Default Attributes** – Creates / refreshes internal baseline attributes (e.g. `remote_id`, `title`) used during mapping and product send flows. All three flows are started automatically (The more category entries there are, the longer the Category Attributes process will take). Product mapping should ONLY begin after Category Node, Category Attributes and Default Attributes flows have completed successfully. **Operational notes & quick checks:** * No CSV or manual trigger is needed for the above maintenance flows. * If one of the flows does not appear or ends in error, check Monitoring > Logs (filter by flow name). Re‑save the channel settings if necessary; if the issue persists contact support. * Avoid re‑saving the channel repeatedly. **Ready for next steps:** Proceed to Section 4 once the Category Node, Category Attributes and Default Attributes flows show success in Logs. \*\*\* End of conflict: retained automatic flows section heading formatting \*\*\* Records that encounter errors in the integration process are temporarily put on hold (penalty). The values for `RETRY_INTERVAL` and `EXPIRATION_DATE` are durations expressed in seconds. * `RETRY_INTERVAL`: Wait time (seconds) before the next retry attempt. * `EXPIRATION_DATE`: Total duration (seconds) added to the first failure time. After this duration the resulting absolute timestamp (`expiration_date`) is passed, no further retries occur. This is a duration, not a stored absolute timestamp. * `MAX_RETRY_COUNT`: Upper limit of total allowed attempts for a single failed record (including the first failed attempt). Condition check: `retry_count < MAX_RETRY_COUNT`. * `sent_to_remote.EXPIRATION_HOUR`: In channel configuration (`FAILED_INTEGRATION.sent_to_remote.EXPIRATION_HOUR`), the maximum hour window during which the remote system (Walmart) response is awaited. `BatchRequest` entries still in `sent_to_remote` or ongoing beyond this window are marked fail (see `finalize_sent_to_remote_batch_requests`). `EXPIRATION_DATE` and `MAX_RETRY_COUNT` jointly restrict retry behavior: * `MAX_RETRY_COUNT`: Stops retries once the limit is reached even if time remains. * `EXPIRATION_DATE`: Stops retries once the time window has elapsed even if the count limit is not reached. Effective retry condition: `(retry_count < MAX_RETRY_COUNT) AND (expiration_date is None OR current_time < expiration_date)`. An integration is eligible for retry only if `retry_count < MAX_RETRY_COUNT` and (if set) current time is before `expiration_date`. Retries stop when either the maximum attempt count is reached or the end timestamp is passed. **Adjusting values based on error volume:** For high error rate processes (e.g. frequently failing product or stock updates), use lower `RETRY_INTERVAL`, `MAX_RETRY_COUNT`, and `EXPIRATION_DATE` so faulty records do not remain long and block others. For low error rates, increase these to allow more retry chances. Optimize according to operational needs and error analysis. In critical flows, as error volume rises, aggressively reduce retry duration and count to preserve stability. Changes to these values apply to subsequently created `FailedIntegration` records. Example: if a SKU stock update fell into penalty with a 3‑hour interval and the interval is changed to 2 hours, the existing record still retries after 3 hours; if it fails again the new record uses the 2‑hour interval. Default Format: ```{ "order": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 3 }, "DEFAULT": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 3 }, "product": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 3 }, "productprice": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 3 }, "productstock": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 3 }, "sent_to_remote": { "EXPIRATION_HOUR": 1 } } ``` Example for product settings when product count is between 100–10,000: ``` ... "product": { "RETRY_INTERVAL": 28800, "EXPIRATION_DATE": 57601, "MAX_RETRY_COUNT": 2 } ... ``` If product count is between 100,000–1,000,000: ``` ... "product": { "RETRY_INTERVAL": 57600, "EXPIRATION_DATE": 105200, "MAX_RETRY_COUNT": 4 } ... ``` **For example:** If a product hits an error while sending to Walmart (missing stock, price data, incomplete mapping, not found, or no response from Walmart within the `sent_to_remote` time), the record is penalized under the current failed integration settings and will not be resent during the penalty window. Additionally, `BatchRequest` entries awaiting remote response that exceed `sent_to_remote.EXPIRATION_HOUR` without a reply are automatically marked fail. This prevents errored or unresponsive operations from blocking healthy records. ## **4. Creation of Category Tree and Development of Attributes for Sales Channel** The category tree is retrieved based on the Category Ids added within the sales channel. Once the category tree is pulled into Omnitron, it can be viewed under the Category Management section when Walmart is selected as the Sales Channel.  Once this process is successfully completed (can be tracked through logs), the flow that retrieves the attributes will automatically be triggered. After the attribute-related processes are finished (if the Default Attribute flow has run and completed successfully), the next steps should be carried out. ## **5. Marketplace Mapping Implementation** After the category tree retrieval step is completed, the user needs to perform category mappings through the Mapper. The Akinon Mapper function within Omnitron allows users to configure and manage the attribute values of products they want to sell on marketplace sales channels according to the marketplace's requirements. It also provides the opportunity to check whether the attributes and attribute values are correct before the products are listed for sale.  The detailed documentation regarding the Mapper and the definitions to be made in the Mapper can be found in [Mapper](https://app.gitbook.com/s/IbwGN7KwvYi0iLbjtnXz/omnitron/sales-channels/sales-channel-settings/how-to-manage-marketplace-mapping-in-omnitron) tutorial. #### **5.1. Product Variants** The schema of variantAttributeNames should be used for product variant mapping on Walmart. A custom mapping similar to the one below should be entered. The \`\`attribute\_set\_id here indicates which field within the product will be used. Since the variant process is based on attribute sets, \`attribute\_set\_id\` has been selected. The keys in the mapping dictionary represent the attribute set ID (Omnitron > Product and Catalogs > Product Attribute Sets). ``` [ { "key": "attribute_set_id", "type": "field", "order": 0, "prefix": "", "is_object": false, "default_value": "" }, { "type": "mapping", "order": 1, "prefix": "", "is_object": false, "mapping_dict": { "1": "color,clothingSize", "2": "color,clothingSize", "3": "color,clothingSize" } } ] ``` ## **6. Adding Products to the Category Tree** On the Walmart side, products need to be added to the relevant category tree. Each product should only be added to one category. Otherwise, an error will occur during the submission process.
| Flag | Description | Frequency |
| get_orders | This flag allows the pulling of orders with the "Created" status from Walmart to Omnitron, going back 12 hours from the flow’s execution time. Before activating this flag, the settings under the second section (Sales Channel Definition) such as Use Cargo Label, Carrier Short Name, Carrier Service Type, Cargo Label Extension, Cargo Company Mapping, Send Shipping Info, Order Start Date, and Use Channel Id In Address Mapping should be properly configured. | It runs every 5 minutes. |
| get_cancel_orders | This flag allows pulling of orders with the "Cancelled" status from Walmart, going back 3 days from the flow's execution time, and ensures that the cancellation plan number in Omnitron is a maximum of 6. Before activating this flag, the settings in the second section (Sales Channel Definition) such as Cancellation Reason Id and Cancellation Mapping should be properly configured. | It runs every 5 minutes. |
| get_refund_orders | This flag allows pulling returns from Walmart on a line-item basis, going back 3 days, and ensures the creation of a return request in Omnitron. Before activating this flag, the settings in the second section (Sales Channel Definition) such as Refund Reason Id and Refund Reason Mapping should be properly configured. | It runs every 5 minutes. |
| send_update_orders | Enables the transmission of the “Shipped” status to Walmart on an item basis by retrieving updated orders along with the “shipping company,” “tracking number,” and “tracking URL” information. Before activating this flag, the Shipping Company Mapping setting under the second section above (Sales Channel Configuration) must be properly configured. This flow also updates the invoice and the order status. | It runs every 5 minutes. |
| send_delete_products | Ensures that products removed from the catalog are marked as retired on Walmart. | It runs every 5 minutes. |
| send_product | Ensures that products that need to be added or updated are sent to Walmart. | Adding runs every 5 minutes, while updating runs every 30 minutes. |
| get_updated_order_items | Sends a request going back 24 hours from the flow's execution time to retrieve item-based orders with the "Shipped" and "Delivered" status from Walmart. It then updates the status and tracking number in Omnitron. Note: For this flow to work, the Send Shipping Info value in the channel config must be set to false. | It runs every 5 minutes. |
| send_updated_product_price | Ensures that product prices that need to be updated are sent to Walmart. | It runs every 5 minutes. |
| send_updated_product_stock | Ensures that product stock updates are sent to Walmart. Before activating this flag, the Buffer Stock setting in the Sales Channel Definition section must be properly configured. | This process runs every minute. |