From VTEX to PostgreSQL: managed, scheduled, no code.
Creating a pipeline that sends data from VTEX to PostgreSQL databases takes only a few minutes with Kondado. And the whole integration from VTEX to PostgreSQL is managed and executed by our platform. With Kondado, you can focus on extracting value from VTEX data and combining it with other data in your PostgreSQL database
How to send VTEX data to PostgreSQL? Kondado provides a direct integration between your VTEX store and PostgreSQL database, allowing you to replicate critical ecommerce data without writing code. Simply select the pipelines you need from the 17 available options covering orders, inventory, and promotions, then configure your preferred update schedule ranging from every 5 minutes to daily intervals. Your data arrives in PostgreSQL ready for analysis, enabling you to build custom reports and combine VTEX information with other business data sources.
Once configured, Kondado automatically maintains your PostgreSQL database with fresh VTEX data, eliminating manual CSV exports and complex API scripting. This streamlined workflow empowers analysts to focus on extracting insights from order details, stock levels, and promotional performance rather than data preparation tasks. The direct pipeline ensures your ecommerce metrics stay synchronized with your analytical environment.
Kondado replicates data from VTEX to PostgreSQL on a configurable schedule, offering 17 distinct pipelines including Orders, Stock, SKUs, and Coupons that deliver 432 fields directly to your database for advanced analytics and reporting.
With the Orders pipeline flowing into your PostgreSQL database, you can analyze transaction patterns and customer behavior using SQL queries to identify trends across different time periods and product categories. The Stock pipeline delivers current inventory positions by warehouse, enabling automated low-stock alerts and sophisticated demand forecasting directly within your database environment without manual spreadsheet updates. Additionally, Marketing Data of Orders provides UTM parameters and affiliate identifiers that allow you to attribute revenue to specific campaigns and optimize your advertising spend through detailed performance analysis in PostgreSQL, creating a comprehensive analytical view of your ecommerce operations.
Try out all the features for free for 14 days
Replicated to PostgreSQL
VTEX data available for PostgreSQL
Tables Kondado writes into your PostgreSQL, on a schedule you control.
17
available pipelines
432
extractable fields
PostgreSQL
Destination
Available integrations
Coupons
Includes fields like coupon_id, expirationintervalperuse, and isarchived, allowing management of promotions and their reuse intervals.
Stock
Presents data such as skuid, warehouseid, and totalquantity, providing information on the stock position of SKUs by warehouse.
Master Data
Contains fields like id, updatedin, and createdin, allowing management of entities and their dynamic properties.
Orders
Includes information such as orderid, status, and totalvalue, allowing detailed tracking of orders and their status.
Shipping Data of Orders
Provides shipping details including shippingestimateddate and shippingestimateddatemax, essential for logistical management.
Marketing Data of Orders
Includes information such as affiliateid and utmcampaign, allowing analysis of marketing campaigns associated with orders.
Order Details
Presents fields like lastmessageunread and callcenteroperatorname, offering insights into customer communication and service.
Logistics Information of Orders
Includes data such as invoiceinput and invoiceoutput, essential for managing fiscal and logistical documents.
Order Items
Contains information about each order item, such as totalitems and paymentnames, allowing detailed analysis of purchased products.
Payments: Order Transactions
Includes details about payment transactions, such as paymentnames and totalvalue, essential for financial control of orders.
Orders: Fees and Benefits
Includes information about fees and benefits associated with orders, such as totalvalue, shippingestimateddate, and paymentnames.
Orders: Totals
Presents the totals of orders, including orderid, totalvalue, and totalitems, along with details about the creation date.
Products
Contains data about available products, including skuid, warehousename, and totalquantity, along with pricing information.
Promotions
Provides details about promotions, including coupon_id, expirationintervalperuse, and maxitemsperclient, along with campaign information.
SKUs
Presents information about SKUs, such as skuid, totalquantity, and reservedquantity, along with data on stock availability.
SKUs: Kits
Includes data about SKU kits, allowing the visualization of product combinations along with their respective quantities and prices.
SKUs: Prices
Provides information about SKU prices, including skuid and pricing details, allowing for cost and promotion analysis.
Sync data automatically — no code, no manual exports.
1
Connect Your VTEX Store
Authenticate your VTEX account in Kondado by providing your API credentials and store identification details to establish the data source connection.
2
Configure PostgreSQL Destination
Enter your PostgreSQL connection parameters including host, database name, and credentials to specify where your VTEX data should land.
3
Select Pipelines and Schedule
Choose from the 17 available VTEX pipelines such as Orders, Stock, and SKUs, then set your preferred update frequency from every 5 minutes to daily intervals.
Try out all the features for free for 14 days
Hundreds of data-driven companies trust Kondado
Why Kondado?
Focus on extracting value from your data and leave the rest to us
Answers about sending VTEX data to PostgreSQL automatically
How does Kondado replicate VTEX data to PostgreSQL?▼
Kondado establishes a direct connection to your VTEX account and extracts data through available pipelines, then loads it into your PostgreSQL database. The process runs automatically on your chosen schedule, handling data transformation and schema management without requiring manual intervention or custom scripts.
What specific VTEX data can I replicate to PostgreSQL?▼
You can choose from 17 available pipelines including Orders, Stock, SKUs, Coupons, Marketing Data, and Order Items, covering 432 distinct fields across your ecommerce operations. This includes transaction details, inventory levels, promotional codes, and shipping information that lands directly in your PostgreSQL database.
How frequently does my VTEX data update in PostgreSQL?▼
Kondado offers configurable update schedules ranging from every 5 minutes to daily intervals, allowing you to balance data freshness with processing requirements. You can adjust these frequencies per pipeline to ensure critical data like Orders updates more frequently than reference data like Master Data.
Can I combine VTEX data with other sources in the same PostgreSQL database?▼
Yes, you can replicate data from additional sources such as Google Sheets, advertising platforms, or ERP systems into the same PostgreSQL instance. This enables comprehensive analysis across your entire business stack, joining VTEX orders with inventory from other channels or marketing spend data.
What format does VTEX data take once it arrives in PostgreSQL?▼
Each pipeline creates structured datasets in PostgreSQL with normalized schemas that maintain relationships between orders, items, and customers. The data arrives ready for SQL querying, allowing you to create views and joins across different VTEX entities without additional processing.
Are there pre-built dashboards available for VTEX data?▼
Yes, Kondado provides ready-made report templates including the VTEX Power BI Report and VTEX Looker Studio Report that connect directly to your replicated data. You can also send data to BigQuery or other destinations if you prefer different visualization tools.
Do I need technical skills to send VTEX data to PostgreSQL?▼
No coding is required to configure the connection, select pipelines, or schedule updates through Kondado's interface. While SQL knowledge helps you analyze the data once it reaches PostgreSQL, the replication process itself requires only your VTEX credentials and database connection details.
'%3E%3Cpath d='M51,41a9.978,9.978,0,0,0-7.857,3.835L22.648,34.588a9.69,9.69,0,0,0,0-5.176l20.5-10.247a10.1,10.1,0,1,0-1.791-3.577L20.857,25.835a10,10,0,1,0,0,12.33L41.352,48.412A9.994,9.994,0,1,0,51,41Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M33,47.645V60.71c.024-.014.05-.018.073-.033l11-7A2,2,0,0,0,45,51.992V40.012Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M31,47.645,19,40.011V51.992a2,2,0,0,0,.927,1.688l11,7c.023.015.049.019.073.033Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M32,21.693l12-7.634L33.076,7.086a2,2,0,0,0-2.152,0L20,14.059Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M12,35.556,0,27.922V39.9A2,2,0,0,0,.927,41.59l11,7c.023.014.049.019.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M52,35.556l12-7.634V39.9a2,2,0,0,1-.927,1.687l-11,7c-.023.014-.049.019-.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M47,38.914a2,2,0,0,0-.924-1.686L38,32.074V27.922l12,7.634V48.621c-.024-.014-.05-.019-.073-.033L47,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M13,33.821l12-7.634L14.076,19.214a2,2,0,0,0-2.152,0L1,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M17,38.914a2,2,0,0,1,.924-1.686L26,32.074V27.922L14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M32,45.91l12-7.634L33.076,31.3a2,2,0,0,0-2.152,0L20,38.276Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M14.076,19.214a2,2,0,0,0-2.152,0L1,26.187l12,7.634,12-7.634Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M49.924,19.214a2,2,0,0,1,2.152,0L63,26.187,51,33.821,39,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M26,27.922,14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726V38.914a2,2,0,0,1,.924-1.686L26,32.074Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M27.076,25.138A2,2,0,0,1,28,26.824V30.8l1.848-1.179A4,4,0,0,1,31,29.123V23.428L19,15.794v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M36.924,25.138A2,2,0,0,0,36,26.824V30.8l-1.848-1.179A4,4,0,0,0,33,29.123V23.428l12-7.634v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M33.076,31.3a2,2,0,0,0-2.152,0L20,38.276,32,45.91l12-7.634Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M50.348,42.573c0-9.411-8.691-12.336-16.348-14.416v-16.1a32.837,32.837,0,0,1,9.363,1.656l2.778,1.11,2.228-5.57L45.584,8.134A38.043,38.043,0,0,0,34,6.046V1H30V6.081c-8.213.594-16.348,4.86-16.348,13.471,0,9.036,8.841,11.732,16.348,13.744V50.074a33.591,33.591,0,0,1-12.006-2.511l-2.683-1.341-2.684,5.367,2.684,1.342c.243.121,5.7,2.792,14.689,3.152V63h4V56.065C44,55.462,50.348,50.3,50.348,42.573Zm-30.7-23.021c0-5.133,5.96-7.016,10.348-7.446V27.071C23.512,25.243,19.652,23.535,19.652,19.552ZM34,50.043V34.393c6.5,1.882,10.348,3.761,10.348,8.18C44.348,48.377,37.873,49.744,34,50.043Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
