VTEX as a Channel
July 21, 2026
Summary
VTEX connects to Flxpoint as a sales channel. The integration publishes product listings to VTEX's catalog, and sends shipment tracking back to VTEX as invoices once an order ships. Connect using your VTEX Server URL, App Key, and App Token; a Seller ID identifies which VTEX account listings publish to.
What this integration does
Publish Listings
Publishes product listings (details, images, pricing and quantity) to VTEX's catalog.
Sync Orders: Send Tracking
Sends shipment tracking to VTEX as an invoice once a Flxpoint order ships.
How to connect: credentials you need
Add a VTEX channel, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your Server URL, App Key, and App Token, then Test Connection → Save Connection.
| Field | What to enter |
|---|---|
Server URLRequired | Your VTEX API server URL, provided by your VTEX account team. |
App KeyRequired | The VTEX App Key generated for your VTEX account. |
App TokenRequired | The App Token paired with your App Key. VTEX only displays it once at creation, so store it securely. |
Seller IDRequired | Identifies which VTEX seller account Publish Listings sends products to. |
App Key and App Token are generated together in VTEX and must belong to the same account as your Server URL and Seller ID. If Test Connection fails, re-generate the App Key/Token pair in VTEX and re-enter all four fields.
Operations: fields to know
Publishes product listings (details, images, pricing and quantity) to VTEX's catalog.
| Field | Maps To: Notes |
|---|---|
| Product Name | → VTEX Product Name. Required. Title shown on the VTEX catalog entry. |
| Product Description | → VTEX Product Description. |
| Brand Name | → VTEX Brand. |
| SKU / Seller SKU ID | → VTEX SKU Name & Seller SKU ID. Required. Identifies the variant to VTEX. |
| Category Full Path | → VTEX Category. Full category path for the listing. |
| Height / Width / Length / Weight | → VTEX Dimensions & Weight. Converted to VTEX's unit scale automatically. |
| Available Quantity | → VTEX Available Quantity. |
| Sale Price / Currency | → VTEX Pricing. Sale price, currency, and currency symbol sent to the listing. |
| Images | → VTEX Images. Variant image URLs attached to the listing. |
| Custom Fields | → VTEX Product / SKU Specifications. Arbitrary name/value fields beyond the standard catalog fields. |
Sends shipment tracking to VTEX as an invoice once a Flxpoint order ships.
| Field | Maps To: Notes |
|---|---|
| Shipment / Order fields you map | → VTEX Invoice. Determines the Tracking Number, Tracking URL, Courier, and Invoice Number sent to VTEX. |
| Ship Date | → VTEX Invoice → Issuance Date. When the invoice/tracking is marked sent. |
| Shipment Item Quantity | → VTEX Invoice Item → Quantity. Required. Units shipped per line. |
| Shipment Item Price | → VTEX Invoice Item → Price. Per-line price on the invoice. |
Common issues
Test Connection fails
The App Key and App Token are generated together in VTEX and must belong to the same account as your Server URL and Seller ID. Re-generate the App Key/Token pair in VTEX and re-enter all four fields.
The App Token is gone
VTEX only displays the App Token once, at creation. If it was not stored, generate a new App Key/Token pair and update the connection.
Listings go to the wrong seller
The Seller ID on the connection identifies which VTEX seller account Publish Listings sends products to. Confirm it against your VTEX account.
FAQs
Which operations does VTEX support?
Two: Publish Listings (details, images, pricing and quantity to the VTEX catalog) and Sync Orders: Send Tracking.
How does tracking reach VTEX?
As a VTEX invoice, sent once the Flxpoint order ships. Your mapping determines the Tracking Number, Tracking URL, Courier and Invoice Number it carries.
Do I need to convert dimensions and weight?
No. Height, width, length and weight are converted to VTEX’s unit scale automatically.