- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Upgrading Pipeline from Standard to Edge
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Pipeline Overview
- Needs Attention
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- Troubleshooting Database Sources
- CockroachDB
- MongoDB
- SharePoint
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Instagram Business
- Amazon Selling Partner
- TikTok Ads
- StackAdapt
- Amazon Ads
- Pinterest Organic
- Zendesk Support
- Snapchat Ads
- TikTok Organic
- Google Search Console
- Klaviyo v2
- Braintree Payments
- Facebook Pages
- Tempo
- PayPal
- Auth0
- Pinterest Ads
- Apple Search Ads
- Permit.io
- Amplitude Analytics
- Customer.io
- Paddle
- Jira Cloud
- Fullstory
- GitHub
- WorkOS
- ActiveCampaign
- Campaign Monitor
- Infobip
- Mailgun Send
- Metaplane
- Notion
- Recharge
- sevdesk
- Statuspage
- Teamwork.com
- Workday RaaS
- Yotpo
- TikTok Shop Partner Center
- Linear
- Microsoft Dynamics 365 Business Central
- Checkout.com
- Pylon
- Increase
- Microsoft Teams
- Rollbar
- Toggl Track
- QuickBooks Online
- Zoho Desk
- Livestorm
- Attentive
- SendGrid
- Bitly
- Shortcut
- Buzzsprout
- Persona
- Mailjet
- Open Exchange Rates
- PagerDuty
- CircleCI
- SonarQube
- Chargebee
- Bing Webmaster Tools
- Rundeck
- Cal.com
- Mixpanel
- Matomo
- Walmart Marketplace
- Xray
- Reddit Ads
- Zoho Recruit
- Freshchat
- Zoho Books
- Outreach
- Airtable
- Attio
- Okta
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Activate
- Custom Connectors
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases-
2026 Releases
- Release 2.53 (August 24 – September 21, 2026)
- Release 2.52 (July 27 – August 24, 2026)
- Release 2.51 (Jun 29 – July 27 , 2026)
- Release 2.50 (Jun 01–29, 2026)
- Release 2.49 (May 04-Jun 01, 2026)
- Release 2.48 (Apr 06-May 04, 2026)
- Release 2.47 (Mar 09-Apr 06, 2026)
- Release 2.46 (Feb 09-Mar 09, 2026)
- Release 2.45 (Jan 12-Feb 09, 2026)
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
-
2026 Releases
- Early Access New
Walmart Marketplace (Edge)
Edge Pipeline is now available for Public Review. You can explore and evaluate its features and share your feedback.
Walmart Marketplace is an online platform that allows approved third-party sellers to list and sell their products on Walmart.com. It enables sellers to manage their item catalog, inventory, pricing, orders, returns, and fulfillment, including Walmart Fulfillment Services (WFS).
Hevo uses the Walmart Marketplace Seller APIs to replicate data from your Walmart Marketplace account to the Destination of your choice. To ingest data, you must provide Hevo with the Client ID and Client Secret of a production API key from your Walmart Marketplace account. Hevo uses these credentials to authenticate with the Walmart Token API using the client credentials grant.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes (for some objects) |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Walmart Marketplace seller account exists from which data is to be ingested.
-
You can access the API Integration page in your Walmart Seller Center account.
-
The Client ID and Client Secret of your production API key are available.
Obtain the Client ID and Client Secret
Hevo connects to your Walmart Marketplace account using the Client ID and Client Secret of your production API key. Hevo uses these credentials to request an access token from the Walmart Token API and reads your data with it.
Perform the following steps to obtain the Client ID and Client Secret:
-
Log in to your Walmart Seller Center account.
-
Go to the API Integration page, and click API Key Management. The Walmart Developer Portal opens, and you are signed in with your Seller Center credentials.
-
Locate your personal key pair, which has a lock icon next to it, and copy the Client ID and the Client Secret. Save them securely like any other password.
Read Get started as a seller for more information.
Note: Use the keys of your production account. Walmart sandbox keys do not work with Hevo.
If the key is regenerated or revoked in the Walmart Developer Portal, Hevo cannot connect to your account, and the Pipeline fails. To resume data ingestion, modify the Source configuration in the Pipeline with the new Client ID and Client Secret.
Configure Walmart Marketplace as a Source in your Pipeline
Perform the following steps to configure your Walmart Marketplace Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Walmart Marketplace.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Walmart Marketplace Source.
-
In the Connect to your Walmart Marketplace seller account section, specify the following:
-
Client ID: The Client ID of your production API key that you obtained from the Walmart Developer Portal. You can change this value after the Pipeline is created.
-
Client Secret: The Client Secret paired with the Client ID. You can change this value after the Pipeline is created.
-
Service Name: The service name that Hevo sends to Walmart in each API request. Default value: Walmart Marketplace. Keep the default value unless Walmart Support has given you a different service name. You can change this value after the Pipeline is created.
-
-
-
Click Test & Continue to test the connection to your Walmart Marketplace Source. Once the test is successful, you can proceed to set up your Destination.
When you click this button, Hevo checks that it can obtain an access token from Walmart with the specified Client ID and Client Secret. If Walmart rejects the credentials, Hevo displays an error message, and you must provide valid production keys.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.
You can select or deselect child objects individually. Deselecting a parent object also deselects all its child objects. Re-selecting a parent object does not re-select its child objects; select them again if you need them.
Hevo ingests the following types of data from your Source objects:
-
Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.
-
Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.
Hevo ingests the objects and their child objects as follows:
| Object | Historical data | Incremental data |
|---|---|---|
| Orders | The orders created in the last 180 days. | The orders modified since the previous run, based on the last modified date. |
| Shipment | The WFS inbound shipments created since January 1, 2020. | The shipments created since the previous run. In addition, Hevo ingests all the shipments again once every seven days to capture updates and deletes. Walmart filters shipments only by creation date, so changes to existing shipments, such as status updates, are captured during the weekly re-ingestion. |
| Unpublished Item | The unpublished items since January 1, 2015. | The items unpublished since the previous run. |
| WFS Inventory Log Payload | The WFS inventory changes of the last 365 days. | The inventory changes since the previous run. |
| Seller Listing Quality Score | The current listing quality score. | The current listing quality score, at most once every hour. |
| Feed Status, Fulfillment Order Status, and Available Report Date | All the records available in the Source. | All the records available in the Source. Records that are no longer available in the Source are retained in the Destination. |
| All other objects | All the records available in the Source. | All the records available in the Source. Records that are no longer available in the Source are marked as deleted. |
For the incremental objects, Hevo ingests the data again from 24 hours before the previous run, to include any records that Walmart updated late.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Walmart Marketplace enforces a rate limit for each seller and each API, using a token bucket in which each API call uses one token and the tokens are refilled at a fixed rate. Hevo paces its requests to remain within these limits. If Walmart still rejects a request with a rate limit exception, Hevo retries it for up to 10 minutes. If the request continues to fail, Hevo ingests the data in the next Pipeline run. Other applications that use the same seller account share these limits with Hevo.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Shipment | Contains the Walmart Fulfillment Services (WFS) inbound shipments that you have created, such as the shipment ID, status, carrier, and expected delivery dates. This object has the following child objects: - Shipment Tracking No - Inbound Shipment Item - Carrier Rate Quote - Shipment Package |
| Item | Contains the items in your Walmart catalog, such as the SKU, product name, lifecycle and publish status, price, and GTIN. This object has the following child objects: - Item Unpublished Reason - Item Additional Attribute - Item Additional Attribute Value |
| Inventory | Contains the inventory available for each SKU across your ship nodes (fulfillment centers). This object has a child object, Inventory Node. |
| Unpublished Item | Contains the items that are not published on Walmart.com, along with details about the item and its offer. |
| Lag Time | Contains the lag time (the number of days between receiving an order and shipping it) configured for each SKU. |
| Promotional Price | Contains the promotional prices configured for each SKU. This object has the following child objects: - Promotional Pricing - Promotional Price Additional Attribute |
| WFS Inventory Log Payload | Contains the GTINs for which Walmart Fulfillment Services inventory activity is logged. This object has a child object, WFS Inventory Log. |
| Price Incentive | Contains the price incentives available for the items in your catalog. |
| Feed Status | Contains the status of the feeds that you have submitted to Walmart, such as the feed ID, feed type, and the number of items received, processed, and failed. This object has the following child objects: - Feed Item Status - Feed Item Detail - Feed Item Ingestion Error - Product Identifier |
| Seller Listing Quality Score | Contains the listing quality score of your seller account and its related metrics. |
| Item Count Listing Quality Issue | Contains the listing quality issue types and the count of items affected by each issue. This object has a child object, Quality Issue Product Type. |
| Repricer Strategy Collection | Contains the repricer strategy collections configured for your account. This object has a child object, Repricer Strategy. |
| Item Taxonomy | Contains the product type taxonomy, that is, the categories used to classify items on Walmart Marketplace. This object has a child object, Item Taxonomy Subcategory. |
| Fulfillment Center | Contains the fulfillment centers (ship nodes) configured for your account, such as the ship node ID, name, address, and status. This object has the following child objects: - Distributor Supported Service - Two Day Shipping Detail - Calendar Day Configuration |
| Fulfillment Center Coverage | Contains the coverage areas served by each of your fulfillment centers. This object has a child object, Coverage Area. |
| Third Party Fulfillment Provider | Contains the third-party fulfillment providers available to your account. |
| Carrier Method | Contains the carrier methods that can be used in your shipping configurations. |
| Fulfillment Order Status | Contains the status of the Walmart Multichannel Solutions (MCS) fulfillment orders, such as the seller order ID, status, and the lines and shipments in the order. This object has the following child objects: - Fulfillment Order Line - Fulfillment Order Line Quantity Info - Fulfillment Order Shipment - Fulfillment Order Shipment Line - Fulfillment Order Shipment Date |
| Inbound Shipment Error Payload | Contains the errors reported for your WFS inbound orders, such as the inbound order ID, the error details, and the items affected. This object has the following child objects: - Inbound Shipment Error - Inbound Shipment Order Item - Add On Service - Dimension |
| Available Report Date | Contains the dates for which a reconciliation report is available for your account, along with the rows of the report for each date. This object has a child object, Recon Report. |
| Payment Statement Report | Contains your payment statement for the current cycle. |
| Performance Report | Contains the performance metrics of your seller account. |
| Orders | Contains the orders placed for your items, such as the purchase order ID, order date, customer order ID, and shipping information. This object has the following child objects: - Order Line - Order Line Status - Order Line Charge - Order Line Refund Charge - Order Pickup Person - Label Detail By Purchase Order - Label Detail Box Item - Label Detail Add On |
| Return | Contains the customer returns for your orders, such as the return ID, customer order ID, and return status. This object has the following child objects: - Return Line Group - Return Line - Return Line Label - Return Line Group Carrier Info List - Return Order Line - Return Order Line Charge - Return Order Line Charge Tax - Return Order Line Charge Reference - Return Order Line Charge Total - Return Order Line Refund Channel - Return Order Line Tracking Detail - Return Order Line Tracking Reference - Return Order Line Current Tracking Status |
| Shipping Template | Contains the shipping templates configured for your account, such as the template ID, name, and status. This object has the following child objects: - Shipping Method - Shipping Method Configuration - Shipping Method Address Type - Shipping Method Tiered Shipping Charge - Shipping Method Region - Shipping Method Sub Region - Shipping Method Sub Region State - Shipping Method State Sub Region |
| Shipping Configuration | Contains the account-level shipping configuration of your seller account. This object has the following child objects: - Shipping Configuration Detail - Shipping Configuration Category |
| Partner Configuration Detail | Contains the configuration details of your seller account, such as the partner ID and feed and API throttling configurations. This object has the following child objects: - Partner Configuration - Partner Configuration Value |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
Walmart Marketplace does not mark records as deleted in its API responses. When a record is deleted, it is no longer returned by the API. Hence, Hevo captures deletes as follows:
-
Objects ingested in full in each run: For all objects except those listed below, Hevo compares the data fetched from the Source with the data present in the Destination table in each run. If a record exists in the Destination but is no longer returned by the Source, Hevo marks it as deleted by setting the value of the metadata column __hevo__marked_deleted to True. This also applies to their child objects.
-
Child objects of Orders, Shipment, and Fulfillment Order Status: When Hevo ingests an updated parent record in an incremental run, it replaces the child records of that parent. Child records that are no longer present in the parent record are removed from the Destination. During a historical load or a resync, the child records are merged and no records are removed. If you resync with Drop and Load, the tables are recreated with the data that Walmart currently returns.
-
Shipment: Hevo ingests all the shipments and their child objects again once every seven days, and marks the shipments and child records that are no longer returned by the Source as deleted. Deletes are marked only when this weekly re-ingestion completes in a single Pipeline run.
-
Promotional Pricing (child object of Promotional Price) and the Shipping Method child objects of Shipping Template: These records are identified by their position in the Walmart response. When Walmart reorders or removes entries, for example, when a promotion expires, the affected records are marked as deleted and loaded again under their new position.
Hevo does not capture deletes for the following objects. Records deleted in the Source remain in the Destination:
-
Available Report Date and its child object, Recon Report
-
Feed Status and its child objects
-
Fulfillment Order Status
-
Orders
-
Seller Listing Quality Score
-
Unpublished Item
-
WFS Inventory Log Payload and its child object, WFS Inventory Log
Source Considerations
-
Walmart returns only the orders created in the last 180 days. As a result, Hevo ingests only the orders created in this period, and an order is no longer updated in the Destination once it is older than 180 days.
-
Walmart provides the data of the following objects only if your seller account is enrolled in the related Walmart program. If your account is not enrolled, these objects and their child objects are displayed as Inaccessible in the Pipeline, and no data is ingested for them:
Walmart program Objects Walmart Fulfillment Services (WFS) Shipment, WFS Inventory Log Payload, and Inbound Shipment Error Payload Multichannel Solutions (MCS) Fulfillment Order Status Repricer Repricer Strategy Collection To ingest data for these objects, enroll in the program in Walmart Seller Center, and then refresh the schema of the Pipeline.
-
If your API key does not have access to an API, the objects that use the API are displayed as Inaccessible in the Pipeline. To ingest data for them, grant the key access to the API in the Walmart Developer Portal.
-
You can also connect using the API key of a Walmart Solution Provider that you have given delegated access to your seller account. The objects that the Solution Provider key cannot access are displayed as Inaccessible in the Pipeline.
-
Walmart lists only the 2,000 most recent feeds. In each run, Hevo ingests these feeds, and retains the feeds ingested in earlier runs after Walmart stops listing them. Feeds that are older than the 2,000 most recent ones when the Pipeline is created cannot be ingested. If more than 2,000 feeds are submitted between two Pipeline runs, the feeds that are no longer listed cannot be ingested, and Hevo displays a warning in Needs Attention.
-
Walmart returns only the orders created in the last 180 days and the 2,000 most recent feeds. If you resync the Orders or Feed Status object, or the Pipeline, with Drop and Load, older orders and feeds that were previously ingested are removed from the Destination and cannot be ingested again.
-
Walmart provides shipping label data only for the orders that you fulfill. Hence, Hevo does not ingest label data for orders fulfilled by WFS.
-
Hevo uses the same API rate limits as the other applications that use your seller account. Running such applications at the same time as the Pipeline can increase the time taken to ingest data.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Nov-06-2026 | 2.54 | New document. |