eBay as a Channel

Table of Contents

How to Connect Listing Operations Order Operations

eBay v2 is our next-generation integration with eBay, leveraging their latest APIs for enhanced listing and inventory management. It allows you to publish new product listings directly from Flxpoint, set a maximum quantity threshold for each item, and sync orders more reliably. While many new features are introduced, legacy functionality from our previous eBay integration is still available for those who prefer familiar processes. By adding eBay v2 as a channel in Flxpoint, you gain a streamlined workflow for creating new listings, updating existing ones, and keeping your orders up to date. This document will guide you through setting up eBay v2, mapping categories, and making the most of these new features to optimize your eBay operations.

How to Connect

Important Note: The new eBay v2 integration is separate from the "legacy" eBay integration.

Do not replace your existing eBay channel yet. Instead, create a new channel for eBay v2 to test.
You can run both side-by-side while testing - your legacy eBay channel will continue to work normally.
Once you've verified that eBay v2 meets all your needs, you can retire your legacy channel.

📋 Phase 1: Channel Creation & Authentication +

Create Your eBay v2 Channel

Choose Your Integration Features

Select which processes you want to enable:

Get Orders - Import orders from eBay to Flxpoint
Publish Listings - Create new listings on eBay (exciting new feature in v2!)
Sync Listings - Update prices and inventory on existing listings
Sync Orders - Send tracking updates back to eBay

Give your channel a descriptive name (e.g., "eBay v2 Store"), then click Save & Next.

Connect to Your eBay Account

On the Connect Channel screen, either:

Select an existing eBay v2 connection, or
Create a new one with your Client ID, Client Secret, and Refresh Token

Need a Refresh Token? After entering your Client ID and Secret, click "Generate a new refresh token" and follow the prompts to authorize Flxpoint with your eBay account.

Click Save Connection and Test Connection to verify everything works, then Save & Next at the confirmation screen.

💲 Phase 2: Pricing, Quantity & Linking +

Configure Pricing Strategy

Under Pricing & Quantity Rules, set up how you want to price your products on eBay:

Add markups (e.g., 20% over cost) or set specific pricing rules
Set minimum prices to protect your margins
Limit quantities shown on eBay (helps prevent overselling)

Set Up Product Linking

In Link Settings, tell Flxpoint how to match your products with existing eBay listings:

SKU → SKU: Your Flxpoint SKU matches eBay's Custom Label
UPC → SKU: Your product UPC matches eBay's Custom Label
Other combinations as needed for your catalog

Pro Tip: If you have multiple identifiers available, set a linking priority order (e.g., try SKU first, then UPC if SKU fails).

In Sync Settings, you can set a maximum quantity limit for all products. This is helpful if you want to be cautious about overselling on eBay.

📝 Phase 3: Publishing Settings & eBay Policies +

Configure eBay Business Policies

If you selected Publish Listings in Phase 1, you'll need to connect your eBay Business Policies. These tell eBay how you handle shipping, returns, and payments:

Return Policy ID - Your return handling policy
Fulfillment Policy ID - Your shipping options and timeframes
Payment Policy ID - How you accept payments
Merchant Location Key - Where you're shipping from

Click "View Policies" and "View Merchant Locations" buttons to see your options from eBay.

Missing Policies? If these fields are empty:

Check that you've created these policies in your eBay Seller Hub
Try regenerating your Refresh Token to fetch the latest data
Contact Flxpoint support if you need help finding your policy IDs

🚚 Phase 4: Order Processing & Shipping +

Configure Order Settings & Shipping

In the Order Fulfillment section, set up how you want to handle eBay orders:

Order Settings - Choose to auto-generate fulfillment requests and avoid duplicates
Shipping Mappings - Match eBay shipping options (like "Expedited") to your internal shipping methods
Get Orders - Set how far back to look for orders (e.g., 7 days) and which status types to import
Sync Orders - Configure when and how to send tracking numbers back to eBay

Shipping Tip: Accurate shipping mappings ensure your customers' shipping expectations are met. Match eBay's shipping speeds with equivalent options in your fulfillment process.

⚙️ Phase 5: Automation & Final Setup +

Schedule Your eBay Processes

In Automate Integrations, decide how often each process should run:

Sync Listings - How often to update prices and inventory (every hour is common)
Publish Listings - How often to create new listings (daily works for most sellers)
Get Orders - How frequently to check for new orders (every 15-30 minutes recommended)
Sync Orders - How often to update tracking info (every few hours is usually sufficient)

You can also leave processes as manual if you prefer to trigger them yourself.

Optional Advanced Settings & Finalization

If needed, configure these additional options to fine-tune your eBay integration:

Advanced Workflows - Custom rules for complex scenarios
Listing Status - Rules for managing product visibility
Invoicing - Customizations for order invoicing

Click Finish or Save & Next through any remaining screens to complete your setup.

Ready to Go Live? After setup, we recommend:

Run each process manually first to test
Verify that a few products sync correctly
Check that test orders process properly
Then enable automation when everything looks good!

📚 eBay Seller Resources & Tips +

eBay Seller Hub: Your command center for all things eBay! Access the Seller Hub here to manage your eBay business.

Publishing New Listings with eBay v2
One of the most exciting features of eBay v2 is the ability to create brand new listings directly from Flxpoint! To make this work well, you'll need:

Valid product identifiers (UPC, SKU)
Complete product data (title, description, images)
eBay leaf category mappings (the most specific category options)
Valid eBay Business Policies (return, payment, fulfillment)

eBay File Export Options

If you prefer working with spreadsheets for bulk updates, you can:

Export your product data from Flxpoint
Download eBay's template from Seller Hub
Combine the data using Excel/Google Sheets
Upload the completed file to eBay

Tips:

Fields in red on eBay's template are required.
Having a valid UPC or Custom Label (SKU) is crucial for linking.

For more details, see our eBay File Export & Linking guide .

Dropshipping & Inventory Tips:
Make sure your Flxpoint inventory is up to date. If using Max Quantity settings, Flxpoint will not show more than that limit even if you have higher stock levels.

Listing Operations

Flxpoint allows you to manage product listings on eBay by syncing inventory, updating product details, and controlling pricing and availability. This ensures accurate and real-time updates across your eBay store.

Import Listings

eBay Legacy integration: Supported.
eBay V2 integration: Not Supported

Import Listings from eBay

Introduction to Import Listings from eBay

The Import Listings integration allows you to pull your existing eBay listings directly into Flxpoint, creating a centralized platform to manage all your products. This integration retrieves comprehensive product details from your eBay account, including titles, descriptions, images, variations, pricing, and inventory quantities. By importing your eBay listings, you can ensure consistency across all your sales channels and simplify your product management workflow.

The Import Listings integration connects your Flxpoint system to eBay to:

Retrieve comprehensive product information from your existing eBay listings
Create a centralized product catalog that includes your eBay inventory
Maintain consistent product data across all your sales channels
Simplify product management by eliminating the need for manual data entry
Enable further synchronization with other marketplaces and platforms

The integration retrieves a comprehensive set of data from your eBay listings:

Product Details: Titles, descriptions, categories, and other basic product information
Images: All product photos attached to your eBay listings
Variations: Size, color, or other attribute options for multi-variation listings
Pricing & Inventory: Current prices and available quantities for each product and variation
Item Identifiers: SKUs, UPCs, EANs, and other product identification numbers
Item Specifics: Brand, MPN, condition, and other product-specific attributes

           API Insight: Under the hood, the integration uses eBay's GetSellerList API call with parameters that retrieve all variations, return full detail, and respect the date range you specify (e.g., last X days). This ensures comprehensive data retrieval while maintaining efficient performance.
        

The Import Listings integration follows a specific process to bring your eBay product data into Flxpoint:

Authentication: Connects to your eBay account using your seller credentials
Data Retrieval: Fetches listings within your specified time frame (e.g., last 7 days)
Data Processing: Transforms eBay's data format into Flxpoint's product structure
Data Mapping: Assigns eBay fields to appropriate product fields in Flxpoint
Product Creation: Creates new products in Flxpoint based on your eBay listings
Product Updating: Updates existing products if they've already been imported previously

Data Flow Process

The integration typically processes data in this sequence:

Retrieves active (and recently ended) listings based on your specified date range
Processes main product data first (titles, descriptions, etc.)
Adds variation data for multi-variation listings
Associates images with appropriate products and variations
Sets pricing and inventory data for each product/variation
Creates or updates products in your Flxpoint catalog

Time-Saving Benefit: By automatically importing your eBay listings, you eliminate the need to manually recreate each product in Flxpoint. A catalog of hundreds or thousands of products can be imported in minutes rather than days of manual data entry.

When setting up the Import Listings integration, you'll configure several key options:

Set New Listings to Paused: Choose whether newly imported listings should be set to "Paused" status, allowing you to review them before they're active in Flxpoint.
Set Your Master SKU: Define which eBay field (often "SKU" or "Item ID") becomes the primary identifier in Flxpoint. This ensures each listing is uniquely recognized and tied to the correct fulfillment source inventory SKU.
Product & Listing Management: Choose whether Flxpoint should "Create and update products & listings" or only "Update existing." This determines how items are added or matched in your catalog.
Import Listings From Last X Days: Specify how far back Flxpoint should look for listings (active or ended). For example, "7" will fetch listings created or modified in the last 7 days.

Advanced Options

Additional configuration options may include:

Category Mapping: Define how eBay categories should map to your internal category structure
Field Transformations: Set up rules for how certain fields should be transformed during import
Image Handling: Configure how product images should be processed and stored
Attribute Mapping: Determine how item specifics from eBay map to product attributes in Flxpoint

           Master SKU Importance: Choosing the right field for your Master SKU is crucial. If your eBay listings have custom SKUs that match your internal inventory system, select "SKU" as your Master SKU field. If not, you might choose "Item ID" or another unique identifier that will help Flxpoint correctly link your products across different systems.
        

Follow these steps to get the Import Listings integration up and running:

1 Connect Your eBay Account: Start by selecting the Import Listings operation in your eBay channel settings. Provide your eBay seller credentials if you haven't already connected an eBay channel.
2 Configure Listing Status: Decide whether newly imported listings should be set to "Paused" status for review or made active immediately. This is especially useful if you want to validate data before it goes live in your system.
3 Set Master SKU Field: Choose which eBay field should serve as the unique identifier in Flxpoint. This is typically "SKU" if your eBay listings have custom SKUs, or "Item ID" if they don't.
4 Choose Product Management Mode: Select whether Flxpoint should "Create and update products & listings" or only "Update existing" items. The former creates new products for any unmatched listings, while the latter only updates products that already exist in Flxpoint.
5 Specify Date Range: Determine how far back Flxpoint should look for listings by setting the "Import Listings From Last X Days" value. Start with a smaller range (e.g., 7 days) to ensure efficient processing, then adjust as needed.
6 Save and Complete: Once you've configured all settings, click the "Save and Complete" button to initiate the import process.
7 Review Imported Products: After the import completes, review the imported products in your Flxpoint catalog to ensure everything was processed correctly.

Initial Import Tip: For your first import, consider setting listings to "Paused" status and using a smaller date range (like 7 days). This allows you to validate the data quality and field mappings before importing your entire catalog. Once confirmed, you can run another import with a larger date range and your preferred status setting.

Implementing the Import Listings integration offers several significant advantages:

Key Benefits

Efficient Management: Keep your eBay listings aligned with other channels in one central dashboard, reducing the need to switch between multiple platforms.
Accurate Data Sync: Ensure that price, inventory, and variants stay current across all your sales channels, reducing the risk of overselling or pricing inconsistencies.
Time-Saving: Eliminate manual data entry by automatically importing complete product information from your eBay listings.
Enhanced Product Data: Leverage the comprehensive data from eBay to enrich your product catalog with detailed descriptions, images, and attributes.
Streamlined Expansion: Simplify the process of expanding to new sales channels by having a complete product catalog ready to publish.

Common Applications

Channel Expansion: Use your eBay product data as a foundation to expand to additional marketplaces without recreating product information.
Inventory Consolidation: Bring all your product data into one system for unified inventory management across multiple sales channels.
Data Migration: When transitioning to a new e-commerce strategy, import your established eBay listings as a starting point.
Multichannel Consistency: Ensure product information remains consistent across all your sales channels by centralizing management in Flxpoint.

Follow these best practices to get the most out of your Import Listings integration:

Start with a Small Date Range: For initial imports, use a smaller date range (e.g., 7 days) to ensure everything works correctly before attempting to import your entire catalog.
Use Paused Status for Review: Set new listings to "Paused" status initially, allowing you to review and validate the imported data before making it active in your system.
Choose Master SKU Carefully: Select a Master SKU field that will reliably identify your products across different systems, ideally using the same identifiers you use in your inventory management.
Schedule Regular Imports: Set up recurring imports to capture any new or updated listings from eBay, ensuring your catalog stays current.
Review and Enrich Data: After import, review your products to identify any areas where data could be enriched or standardized to improve consistency across channels.
Map Categories Consistently: Ensure eBay categories map logically to your internal category structure for better organization and searching.

           Organization Tip: Consider adding a tag or custom field to imported products indicating they came from eBay. This can help you track the source of your products and apply channel-specific rules or workflows if needed.
        

If you encounter issues with the Import Listings integration, here are some common problems and solutions:

No Listings Imported: Verify your date range isn't too restrictive. If you set "Last 1 Day" but haven't listed anything new in 24 hours, try extending to 7 or 30 days.
Missing Images: Ensure your eBay listings have properly linked images. The integration can only import images that are already associated with your eBay listings.
Incomplete Variation Data: Check that your multi-variation listings on eBay have all necessary information for each variation. Missing data on eBay will result in missing data in Flxpoint.
Authentication Errors: If you receive authentication errors, verify your eBay credentials are correct and your seller account is in good standing with eBay.
Duplicate Products: If you see duplicate products after import, check your Master SKU configuration. Using inconsistent identifiers can lead to duplicate product creation.

Diagnostic Tip: If you're experiencing issues, try importing a single, simple listing first by setting a very recent date range that only includes that listing. This allows you to troubleshoot with a minimal test case rather than your entire catalog.

Conclusion

The Import Listings integration provides a powerful way to bring your existing eBay product catalog into Flxpoint, enabling centralized management across all your sales channels. By correctly configuring the integration options and following best practices, you can efficiently import comprehensive product data without manual entry, ensuring consistency and accuracy throughout your e-commerce ecosystem. Once your listings are imported, you can leverage Flxpoint's additional features to further enhance and distribute your product information across multiple platforms.

Sync & Link Listings

eBay V2 integration: Supported
eBay Legacy integration: Supported

Sync & Link Listings: eBay Legacy vs. eBay v2

Introduction to Sync & Link Listings

The Sync & Link Listings operations allow you to manage existing eBay listings directly from Flxpoint without republishing them. These powerful tools enable you to keep your eBay listings in sync with your Flxpoint catalog, ensuring consistent pricing and inventory across all your sales channels. Whether you're using the Legacy or v2 version of the eBay integration, these operations provide essential functionality for multichannel sellers.

The Sync & Link Listings operations serve two primary purposes:

Sync Listings: Push or pull updated price and quantity information between Flxpoint and eBay, ensuring your listings always have current data.
Link Listings: Match existing eBay listings with products in your Flxpoint catalog so they stay in sync over time, eliminating the need to recreate listings.

           Key Benefit: These operations allow you to maintain and update existing eBay listings rather than deleting and republishing them. This preserves your listing history, feedback, and search ranking while still keeping information current.
        

While both versions accomplish the same goals, there are important differences between eBay Legacy and eBay v2 integrations:

API Technology

eBay Legacy: Uses eBay's Trading API with GetSellerList calls in small batches
eBay v2: Uses newer REST API endpoints for better performance and scalability

Key Differences

Feature	eBay Legacy	eBay v2
Channel Setup	Uses existing eBay channel configuration	Typically requires creating a new channel rather than replacing the old one
Authentication	Uses Auth Token system	Uses OAuth2 credentials with better security
Policy IDs	Not typically required	Relies on numeric Return, Payment, and Fulfillment policy IDs
Maximum Quantity	Basic quantity control	More robust Maximum Quantity feature to cap displayed inventory
Category Handling	More flexible	Requires valid numeric leaf category IDs
Batch Processing	GetSellerList calls in chunks	REST inventory endpoints for bulk operations

           Recommendation: For new eBay integrations, v2 is generally recommended as it uses eBay's newer API architecture with better performance and additional features. However, if you have an existing Legacy implementation, it continues to be fully supported.
        

The Sync Listings operation keeps your price and inventory information current between Flxpoint and eBay:

Purpose

The primary purpose of Sync Listings is to maintain accurate price and quantity information, typically pushing data from Flxpoint to eBay. This ensures your eBay listings always reflect your current prices and available inventory.

Key Features

Bidirectional Sync: Choose whether to push changes from Flxpoint to eBay or pull changes from eBay to Flxpoint (most commonly from Flxpoint to eBay)
Maximum Quantity: Set a cap on the quantity shown on eBay, even if your actual inventory is higher
Inventory Control: Hide, unhide, or delist products entirely based on inventory conditions or business rules
Variant Management: Update individual variants within a multi-variation listing

Hiding, Unhiding, and Delisting

With both Legacy and v2 integrations, you can:

Hide: Temporarily remove a product or specific variant from visibility on eBay while maintaining the listing
Unhide: Make a previously hidden product or variant visible again
Delist: Completely remove a listing from eBay

While the functionality is similar, v2 uses different API calls behind the scenes, referring to these operations as bulk update or inventory item group calls.

Inventory Protection Example: If you set a Maximum Quantity of 5 for your eBay listings, even if you have 50 units in stock, eBay will only show 5 available. This protects you from overselling if there are unexpected spikes in demand across your sales channels.

The Link Listings operation connects your existing eBay listings to products in your Flxpoint catalog:

Purpose

Link Listings matches your existing eBay listings to the corresponding products in Flxpoint, establishing connections that allow for ongoing synchronization without republishing. This is essential for maintaining consistency across platforms while preserving your listing history and performance metrics.

Key Features

Linking Priority: Choose which fields Flxpoint should compare first (e.g., SKU, UPC, MPN) to find matches
Batch Retrieval: Process listings in manageable chunks to ensure efficient performance
Match Verification: Review and confirm matches to ensure accuracy
Broken Link Detection: Identify when listings have been removed from eBay

Linking Priority

Linking Priority is a crucial setting that determines how Flxpoint matches eBay listings to your catalog:

Fields are tried in order, from top to bottom, until a match is found
Common priorities include SKU, UPC, MPN, or other unique identifiers
This is especially important if your eBay listings use different SKUs than your internal catalog

If You Delete a Product on eBay

If you remove a product on eBay, it remains "Linked" in Flxpoint until the next sync. Then it's marked as "Broken Link." You can manually unlink it in Flxpoint if you no longer want that connection.

Linking Strategy: For the most reliable linking, ensure your eBay listings contain the same unique identifiers (SKUs, UPCs, etc.) as your Flxpoint catalog. If they don't match exactly, prioritize the most consistent identifiers first in your Linking Priority list.

eBay v2 has specific requirements for category handling that differ from Legacy:

Leaf Category IDs

eBay v2 requires valid leaf category IDs—numeric codes that identify specific categories in eBay's extensive category tree. These IDs can be challenging to work with because:

They are numeric codes rather than descriptive names
eBay's category tree contains tens of thousands of options
Categories are regularly updated by eBay
You must use the exact leaf (bottom-level) category ID

Using Mapping Sets

To simplify category management, create a mapping set in Flxpoint that translates your internal category names to the corresponding eBay numeric IDs:

Go to Account Settings in Flxpoint and create a new Mapping Set
Name it something like "eBay Category IDs"
Add entries that map your internal category names to eBay's numeric IDs
For example: "Clothing > Men's > Shirts" → "57990"
Select this mapping set when configuring your Sync & Link operations

This approach allows you to work with familiar category names internally while ensuring the correct numeric IDs are sent to eBay.

           Resource Tip: eBay provides category files that list all valid category IDs. Download these files from eBay's developer portal to build your category mapping set. Update your mappings periodically as eBay updates its category structure.
        

Follow these steps to set up the Sync & Link Listings operations:

eBay Legacy Setup

eBay v2 Setup

1 Access Your eBay Channel: Navigate to your existing eBay channel in Flxpoint
2 Add Sync & Link Operations: Enable the Sync Listings and Link Listings operations
3 Configure Sync Settings: Choose data flow direction (typically Flxpoint to eBay) and set any quantity limits
4 Set Linking Priority: Arrange identifier fields (SKU, UPC, etc.) in order of matching priority
5 Create Mapping Template: Define how fields like SKU, Quantity, and Price map between systems
6 Save and Complete: Save your configuration to activate the operations
7 Run Initial Link: Execute Link Listings first to establish connections
8 Run Initial Sync: Run Sync Listings to update information

1 Create a New Channel: For v2, create a completely new eBay channel rather than replacing your existing Legacy channel
2 Provide OAuth Credentials: Enter your eBay v2 OAuth credentials
3 Add Sync & Link Operations: Enable the Sync Listings and Link Listings operations
4 Configure Policy IDs: Set up Return, Payment, and Fulfillment policy IDs (Flxpoint can pull these automatically)
5 Configure Sync Settings: Choose data flow direction and set Maximum Quantity if needed
6 Set Linking Priority: Arrange identifier fields in order of matching priority
7 Create Category Mapping Set: Set up mappings for eBay's numeric category IDs
8 Create Mapping Template: Define field mappings, ensuring Category ID is properly mapped via your mapping set
9 Save and Complete: Save your configuration to activate the operations
10 Run Initial Link: Execute Link Listings first to establish connections
11 Run Initial Sync: Run Sync Listings to update information

           Important: Always run Link Listings before Sync Listings when first setting up these operations. Linking establishes the connections between systems that the Sync operation depends on.
        

Follow these best practices to get the most out of Sync & Link Listings:

Use Consistent Identifiers: Ensure your eBay listings and Flxpoint products use the same unique identifiers (SKUs, UPCs, etc.) to make linking reliable.
Set Appropriate Sync Schedule: Configure automatic syncs to run frequently enough to keep data current, but not so often that you hit API rate limits (typically every few hours).
Consider Maximum Quantity: Use the Maximum Quantity feature to prevent overselling, especially if you sell on multiple channels.
Test with Small Batches: When first setting up, test with a small subset of listings before processing your entire catalog.
Keep Category Mappings Updated: For v2, regularly update your category mapping set as eBay changes its category structure.
Monitor Broken Links: Regularly check for and resolve broken links to maintain system integrity.
Run Link Before Sync: When making significant changes, run Link Listings before Sync Listings to ensure connections are current.

Efficiency Tip: Consider setting up different sync schedules based on product type or importance. For fast-moving inventory, sync more frequently, while slower-moving inventory can be synced less often to conserve API calls.

If you encounter issues with Sync & Link Listings, here are some common problems and solutions:

Listings Not Linking: Verify your Linking Priority settings and ensure the identifiers in both systems match. Check for extra spaces or formatting differences in SKUs.
Price or Quantity Not Updating: Confirm your mapping template correctly maps these fields and that the direction of sync (Flxpoint to eBay vs. eBay to Flxpoint) is set appropriately.
Category Errors (v2): Ensure you're using valid leaf category IDs. Invalid category IDs are a common cause of sync failures in v2.
Authentication Issues: For Legacy, check that your Auth Token is valid. For v2, refresh your OAuth credentials if they've expired.
API Rate Limits: If you're processing a large catalog, you might hit eBay's API rate limits. Space out your operations or reduce batch sizes.
Broken Links Appearing: This usually indicates the listing was removed from eBay. Verify in your eBay Seller Hub and either unlink the product or republish if needed.

           Diagnostic Approach: When troubleshooting, start by verifying a single listing's sync process from end to end. Confirm it links properly, then check if pricing and inventory updates work correctly. Once you've resolved issues with a single listing, apply the solution to your broader catalog.
        

Conclusion

The Sync & Link Listings operations provide powerful tools for managing existing eBay listings through Flxpoint, allowing you to maintain consistent pricing and inventory across channels without republishing. Whether you choose eBay Legacy or the newer v2 integration, these operations help streamline your multichannel selling strategy by keeping your eBay marketplace aligned with your central product catalog. By properly configuring linking priorities, mapping templates, and sync settings, you can automate updates and prevent overselling while preserving your valuable eBay listing history and search ranking.

Publish Listings

eBay V2 integration: Supported
eBay Legacy integration: Not supported.

Supported | Publish Listings

Introduction to Publish Listings

The Publish Listings feature enables you to map and configure your product data for seamless publishing to eBay. Whether you're listing new products or managing a large catalog, this tool ensures your source data aligns with eBay’s required fields, creating accurate and compliant listings. For a complete list of valid eBay US leaf categories, download this XLSX file.

The Publish Listings section connects your product data to eBay’s platform, allowing you to:

Map source data to eBay’s required fields for precise and compliant listings.
Configure settings to control publishing, including options to avoid fees like those for subtitles.
Customize and manage listing templates for different product types or categories, streamlining your workflow.

           Key Benefit: Ensures listings are accurate, optimized, and cost-efficient, saving time and reducing errors.
        

The mapping process links your source data fields to eBay’s listing fields:

Template Creation: Create a mapping template to define data connections.
Data Alignment: Ensure correct information (e.g., title, price) is sent to eBay.
Reusability: Save templates for reuse, saving time.

Note: Incorrect mappings can cause listing failures or incomplete data display.

Customize listings with these settings:

Field Mapping: Map source fields (e.g., “Product Name”) to eBay fields (e.g., “Title”).
Subtitle Fees: Set “Subtitle” to “Don’t Map” to avoid fees.
Category Selection: Use valid eBay category IDs from the XLSX file.
Business Policies & Merchant Location: Provide valid Return, Fulfillment, Payment policy IDs, and a Merchant Location Key. If missing:
- Generate an eBay v2 Refresh Token via Connect Channel.
- Create policies in eBay’s Business Policy section.
- Set up a Merchant Location in eBay if required.

           Resource Tip: Download eBay’s category file for valid IDs and update mappings periodically.
        

Follow these steps to configure your Publish Listings template:

eBay v2 Setup

1 Create a New Template: Name it (e.g., “eBay Electronics Mapping”) for organization.
2 Map Fields: Link source data to eBay fields (e.g., “Product Name” to “Title”).
3 Configure Subtitles: Set “Subtitle” to “Don’t Map” to avoid fees.
4 Configure Policy IDs: Set up Return, Payment, and Fulfillment policy IDs (Flxpoint can pull these).
5 Create Category Mapping Set: Map internal categories to eBay numeric IDs.
6 Save and Use: Save the template and apply it when publishing.

           Important: Verify all required fields are mapped to prevent publishing failures.
        

A mapping template defines how source data translates to eBay fields.

Interface Overview

Screen labeled “Publish Products.” Name your template (e.g., “eBay Clothing Mapping”).
Buttons: Delete, Duplicate, Save.
Columns: From Value (source fields/static values) and To eBay Field (eBay fields).

Mapping Options

Don’t Map: Ignore the field (e.g., “Subtitle”).
Set To Empty: Map but leave blank.
Field: Link a source field.
Value: Set a static value (e.g., “VAT Percentage” to “20”).
Mapping Set: Apply predefined mappings.
Rules: Use conditional logic.

Available eBay Fields

eBay v2 Fields: Description, Title, Subtitle, Third Party Tax Category, UPC, VAT Percentage, eBay Plus If Eligible.
Category Aspects: Up to 10 sub-aspects per category.

Complete Field Mappings

Field	Example	Suggested Mapping	Reason
Title	Wireless Bluetooth Headphones	Map to “Title” using “Field.”	Matches product name.
Description	High-quality headphones.	Map to “Description” using “Field.”	Provides product details.
Subtitle	Free Shipping Included	Set to “Don’t Map.”	Avoids fees.
Third Party Tax Category	Electronics	Map to “Tax Category” or “Don’t Map.”	Ensures tax compliance.
UPC	012345678905	Map to “UPC” using “Field.”	Required for many categories.
VAT Percentage	20	Set to “Value” (e.g., “20”).	Ensures tax compliance.
eBay Plus If Eligible	Boolean	Map or “Don’t Map.”	Optional for eBay Plus.

Source Data Fields

Listing Parent: Attribute (K/V), Brand (T), Category 1-3 (T), Custom Field (K/V), Description (T), Image (L), Parent SKU (T), Title (T).
Listing Variant: ASIN (T), Custom Field (K/V), Description (T), Dimensional Weight (N), Estimated Cost (N), GTIN (T), Height (N), Image (L), Length (N), List Price (N), MAP (N), MPN (T), MSRP (N), Master SKU (T), Option (K/V), Quantity (N), SKU (T), Title (T), UPC (T), Weight (N), Width (N).

Practice Mapping

Try mapping the “Title” field:

Follow these best practices for optimal use of Publish Listings:

Ensure Accurate Mappings: Double-check that all required fields (e.g., Title, UPC) are correctly mapped to avoid listing failures.
Avoid Subtitle Fees: Always set the “Subtitle” field to “Don’t Map” unless you intentionally want to incur extra fees.
Use Valid Category IDs: Regularly update your category mappings using eBay’s category file to ensure compliance with eBay’s structure.
Test Small Batches: Start with a few products to verify mappings before publishing your entire catalog.
Configure Policies Early: Set up Return, Fulfillment, and Payment policies in eBay Seller Hub before configuring Flxpoint to avoid delays.

Efficiency Tip: Create separate mapping templates for different product categories (e.g., Electronics, Clothing) to streamline publishing and reduce errors.

Common issues and solutions:

Missing Fields: Map all required fields (e.g., Title, UPC).
Incorrect Category IDs: Verify IDs from the XLSX file.
Subtitle Fees: Set “Subtitle” to “Don’t Map” and re-save.
eBay Motors: Not supported; use a verified eBay Motors account and upload manually (support estimated in 1–2 sprints).
Missing Policy Fields: Ensure:
- Refresh Token generated via “Connect Channel.”
- Policies created in eBay Seller Hub (Account > Business Policies).
- Merchant Location set in eBay.
- Click “View Policies” or “View Merchant Locations” in Flxpoint.

           Diagnostic Tip: Test with one product to verify mappings before publishing the catalog.
        

Conclusion

With a configured Publish Listings template, you can publish accurate eBay listings efficiently. Map fields carefully, set “Subtitle” to “Don’t Map” to avoid fees, and use valid category IDs. Set up eBay Business Policies and Merchant Location for smooth operations. You’re ready to grow your eBay presence!

Order Operations

Flxpoint imports orders from eBay into your system, automating order processing, tracking updates, and inventory adjustments. This streamlines fulfillment and ensures efficient handling of eBay transactions.

Get Orders

eBay V2 integration: Supported
eBay Legacy integration: Supported

Supported | Get Orders

Introduction to Get Orders

The Get Orders operation retrieves order data from eBay and maps it into Flxpoint for processing. This guide details every field in the eBay Get Orders mapping template, helping you manage orders whether using eBay Legacy or eBay v2 integrations.

The Get Orders operation connects eBay order data to Flxpoint, enabling you to:

Map eBay order fields to Flxpoint fields for accurate order management.
Customize how data is handled with mapping modes like Don’t Map, Field, or Rules.
Ensure seamless order fulfillment, inventory updates, and customer service across platforms.

           Key Benefit: Automates the import of eBay orders into Flxpoint, ensuring consistency and reducing manual data entry errors.
        

The mapping process links eBay order data fields to Flxpoint order fields:

Template Creation: Define mappings in a template to connect eBay data to Flxpoint fields.
Data Alignment: Ensure accurate data transfer (e.g., eBay Order ID to Flxpoint External Order ID).
Reusability: Save templates for consistent use across imports.

Note: Incorrect mappings can lead to missing or mismatched data in Flxpoint.

Customize your order imports with these settings:

Mapping Modes: Choose how to handle each field:
- Don’t Map: Ignore the field.
- Set To Empty: Clear the Flxpoint field.
- Field: Copy eBay data directly.
- Value: Set a static value (e.g., “Marketplace” to “eBay”).
- Mapping Set: Transform data using a lookup table.
- Rules: Apply conditional logic (e.g., if “ShipCountry=CA,” set “OrderType=International”).
Fulfillment Status Filtering: Filter orders by status (e.g., “Not Started,” “In Progress”).
Fetch Last X Days: Limit how far back to retrieve orders (e.g., 7 days).
PII Retention: Set retention periods for buyer details to comply with privacy laws.
Shipping Mappings: Map eBay shipping methods to Flxpoint formats.

           Resource Tip: Use the Shipping Mappings screen to unify eBay shipping methods for accurate order processing.
        

Follow these steps to configure your Get Orders template:

eBay v2 Setup

1 Create a New Template: Name it (e.g., “eBay Orders Mapping”) for organization.
2 Map Fields: Link eBay fields to Flxpoint fields (e.g., “eBay Order ID” to “External Order ID”).
3 Configure Filters: Set Fulfillment Status to “In Progress” or “Not Started” to focus on actionable orders.
4 Set Fetch Period: Choose “7” days to avoid duplicates.
5 Configure Shipping Mappings: Map eBay shipping methods to Flxpoint formats.
6 Save and Use: Save the template and apply it to import orders.

           Important: Test your mappings with a small batch of orders to ensure correct data import.
        

A mapping template defines how eBay order data translates to Flxpoint fields.

Interface Overview

Screen labeled “Get Orders.” Name your template (e.g., “eBay Orders Mapping”).
Buttons: Delete, Duplicate, Save.
Two columns: From Value (eBay fields) and To Flxpoint Field (Flxpoint fields).

Mapping Options

Don’t Map: Ignore the field.
Set To Empty: Clear the field.
Field: Direct mapping (e.g., “eBay Order ID” to “External Order ID”).
Value: Static value (e.g., “Marketplace” to “eBay”).
Mapping Set: Use a lookup table (e.g., for shipping methods).
Rules: Conditional logic (e.g., if “ShipCountry=CA,” set “OrderType=International”).

Available eBay Fields

eBay Buyer Registration Address: Address Line 1, Full Name, Email, etc.
eBay Order: Order ID, Creation Date, Fulfillment Status, Total, etc.
eBay Order Item: SKU, Quantity, Line Item Cost, Gift Message, etc.
eBay Order Payment: Payment Method, Payment Date, Reference ID, etc.
eBay Order Pricing Summary: Total, Tax, Delivery Cost, etc.
eBay Order Refund: Refund Amount, Refund Date, Status, etc.

Complete Field Mappings

Category	Field	Data Type	Suggested Mapping	Reason
eBay Buyer Registration Address
	Address Line 1Primary billing address line, e.g., 123 Main St.	T	Map to “Billing Address 1” using “Field.”	Ensures billing address accuracy.
	Address Line 2Secondary billing address line, e.g., Apt 4B.	T	Map to “Billing Address 2” using “Field.”	Provides additional address details.
	CityBilling city, e.g., New York.	T	Map to “Billing City” using “Field.”	Specifies the billing city.
	Company NameCompany name for billing, e.g., Acme Corp.	T	Map to “Billing Company” or “Don’t Map.”	Optional for business orders.
	CountryBilling country, e.g., USA.	T	Map to “Billing Country” using “Field.”	Identifies the billing country.
	Country CodeBilling country code, e.g., US.	T	Map to “Billing Country Code” using “Field.”	Standardizes country identification.
	EmailBuyer’s email, e.g., buyer@example.com.	T	Map to “Customer Email” using “Field.”	Ensures contact information is captured.
	Full NameBuyer’s full name, e.g., John Doe.	T	Map to “Customer Name” using “Field.”	Identifies the buyer.
	PhoneBuyer’s phone number, e.g., 555-123-4567.	T	Map to “Customer Phone” using “Field.”	Provides contact number for communication.
	Postal CodeBilling postal code, e.g., 10001.	T	Map to “Billing Zip” using “Field.”	Ensures accurate billing location.
	State or ProvinceBilling state, e.g., NY.	T	Map to “Billing State” using “Field.”	Specifies the billing state.
eBay Buyer Tax Address
	CityTax jurisdiction city, e.g., New York.	T	Map to “Tax City” using “Field.”	Specifies the tax jurisdiction city.
	Country CodeTax jurisdiction country code, e.g., US.	T	Map to “Tax Country Code” using “Field.”	Identifies the tax country.
	Postal CodeTax jurisdiction postal code, e.g., 10001.	T	Map to “Tax Zip” using “Field.”	Ensures accurate tax location.
	State or ProvinceTax jurisdiction state, e.g., NY.	T	Map to “Tax State” using “Field.”	Specifies the tax jurisdiction state.
eBay Buyer Tax Identifier
	Issuing CountryCountry issuing the tax ID, e.g., US.	T	Map to “Tax Issuing Country” or “Don’t Map.”	Optional for tax compliance.
	Tax Identifier TypeType of tax ID, e.g., VAT.	T	Map to “Tax ID Type” or “Don’t Map.”	Identifies the type of tax ID.
	Taxpayer IDBuyer’s tax ID, e.g., 123-45-6789.	T	Map to “Taxpayer ID” or “Don’t Map.”	Tracks the buyer’s tax ID for compliance.
eBay Order
	Authenticity Verification Outcome ReasonReason for authenticity outcome, e.g., Item not authentic.	T	“Don’t Map” or custom field.	Optional for verification issues.
	Authenticity Verification StatusStatus of authenticity check, e.g., Passed.	T	“Don’t Map” or custom field.	Optional for authenticity checks.
	Buyer Checkout NotesNotes from buyer, e.g., Please ship quickly.	T	Map to “Order Notes” using “Field.”	Captures buyer instructions.
	Buyer UsernameBuyer’s eBay username, e.g., buyer123.	T	Map to “Customer Name” using “Field.”	Identifies the buyer.
	Cancel StateCancellation status, e.g., Cancelled.	T	Map to “Order Status” or “Don’t Map.”	Tracks cancellation status.
	Cancelled DateDate of cancellation, e.g., 2025-05-20.	D	Map to “Cancel Date” or “Don’t Map.”	Records cancellation date.
	Creation DateDate order was placed, e.g., 2025-05-20.	D	Map to “Order Date” using “Field.”	Records when the order was placed.
	Fulfilled ByParty fulfilling the order, e.g., eBay.	T	Map to “Fulfilled By” or “Don’t Map.”	Identifies fulfillment party.
	Last Modified DateDate of last update, e.g., 2025-05-20.	D	Map to “Last Modified” or “Don’t Map.”	Tracks order updates.
	Legacy Order IDLegacy order identifier, e.g., OLD-123.	T	Map to “Legacy Order ID” or “Don’t Map.”	Supports legacy systems.
	Order Fulfillment StatusFulfillment progress, e.g., In Progress.	T	Map to “Fulfillment State” using “Field.”	Tracks shipping progress.
	Order IDUnique order identifier, e.g., 123456-789.	T	Map to “External Order ID” using “Field.”	Ensures unique order identification.
	Order Payment StatusPayment status, e.g., Paid.	T	Map to “Payment Status” using “Field.”	Tracks payment status.
	Sales Record ReferenceeBay invoice reference, e.g., SR-123.	T	Map to “Invoice Number” using “Field.”	Links to eBay invoice.
	Seller IDSeller identifier, e.g., seller123.	T	Map to “Seller ID” or “Don’t Map.”	Identifies the seller.
	Total Due SellerAmount due to seller, e.g., 50.00.	N	Map to “Total Due Seller” or “Don’t Map.”	Tracks amount due to seller.
	Total Due Seller CurrencyCurrency for amount due, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for amount due.
	Total Fee Basis AmountBasis for fees, e.g., 45.00.	N	“Don’t Map” or custom field.	Optional for fee calculations.
	Total Fee Basis Amount CurrencyCurrency for fee basis, e.g., USD.	T	“Don’t Map” or custom field.	Optional for fee currency.
	Total Marketplace FeeMarketplace fee, e.g., 5.00.	N	“Don’t Map” or custom field.	Optional for marketplace fees.
	Total Marketplace Fee CurrencyCurrency for marketplace fee, e.g., USD.	T	“Don’t Map” or custom field.	Optional for fee currency.
	eBay International Shipping Returns Managed ByEntity managing returns, e.g., eBay.	T	“Don’t Map” or custom field.	Optional for international shipping.
	eBay Shipping Label Provided ByProvider of shipping label, e.g., eBay.	T	“Don’t Map” or custom field.	Optional for shipping labels.
	eBay Vault Fulfillment TypeType of vault fulfillment, e.g., Standard.	T	“Don’t Map” or custom field.	Optional for vault fulfillment.
eBay Order Fulfillment Appointment
	Appointment End DateEnd date of appointment, e.g., 2025-05-20.	D	“Don’t Map” or custom field.	Optional for appointment scheduling.
	Appointment Start DateStart date of appointment, e.g., 2025-05-20.	D	“Don’t Map” or custom field.	Optional for appointment scheduling.
	Appointment TypeType of appointment, e.g., Delivery.	T	“Don’t Map” or custom field.	Optional for appointment type.
	Appointment StatusStatus of appointment, e.g., Scheduled.	T	“Don’t Map” or custom field.	Optional for appointment status.
	Appointment WindowTime window for appointment, e.g., 9 AM - 12 PM.	T	“Don’t Map” or custom field.	Optional for appointment window.
	Service Provider Appointment DateProvider’s appointment date, e.g., 2025-05-20.	D	“Don’t Map” or custom field.	Optional for provider scheduling.
eBay Order Fulfillment Destination Address
	Address Line 1Primary destination address, e.g., 456 Oak St.	T	Map to “Destination Address 1” using “Field.”	Ensures accurate delivery address.
	Address Line 2Secondary destination address, e.g., Suite 200.	T	Map to “Destination Address 2” using “Field.”	Provides additional address details.
	CityDestination city, e.g., Los Angeles.	T	Map to “Destination City” using “Field.”	Specifies the delivery city.
	CountryDestination country, e.g., USA.	T	Map to “Destination Country” using “Field.”	Identifies the delivery country.
	Country CodeDestination country code, e.g., US.	T	Map to “Destination Country Code” using “Field.”	Standardizes country identification.
	Postal CodeDestination postal code, e.g., 90001.	T	Map to “Destination Zip” using “Field.”	Ensures accurate delivery location.
	State or ProvinceDestination state, e.g., CA.	T	Map to “Destination State” using “Field.”	Specifies the delivery state.
eBay Order Fulfillment Instructions
	Destination TimezoneTimezone of destination, e.g., PST.	T	“Don’t Map” or custom field.	Optional for delivery scheduling.
	Fulfillment Instruction TypeType of instruction, e.g., Standard.	T	“Don’t Map” or custom field.	Optional for fulfillment instructions.
	Max Estimated Delivery DateLatest delivery date, e.g., 2025-05-25.	D	Map to “Max Delivery Date” or “Don’t Map.”	Provides delivery estimate.
	Min Estimated Delivery DateEarliest delivery date, e.g., 2025-05-22.	D	Map to “Min Delivery Date” or “Don’t Map.”	Provides delivery estimate.
	Pickup Merchant Location KeyKey for pickup location, e.g., LOC-123.	T	“Don’t Map” or custom field.	Optional for pickup locations.
eBay Order Fulfillment Shipping Step
	Ship To Reference IDReference ID for shipping, e.g., REF-456.	T	“Don’t Map” or custom field.	Optional for shipping reference.
	Shipping Carrier CodeCarrier code, e.g., USPS.	T	Map to “Shipping Carrier” using “Field.”	Identifies the carrier for shipping.
	Shipping Service CodeShipping method, e.g., USPS Priority Mail.	T	Map to “Shipping Method” using “Mapping Set.”	Ensures consistent shipping method formats.
eBay Order Fulfillment Ship To Address
	Address Line 1Primary shipping address, e.g., 789 Pine St.	T	Map to “Shipping Address 1” using “Field.”	Ensures accurate shipping address.
	Address Line 2Secondary shipping address, e.g., Unit 5.	T	Map to “Shipping Address 2” using “Field.”	Provides additional address details.
	CityShipping city, e.g., Chicago.	T	Map to “Shipping City” using “Field.”	Specifies the shipping city.
	Company NameShipping company name, e.g., XYZ Inc.	T	Map to “Shipping Company” or “Don’t Map.”	Optional for business shipments.
	CountryShipping country, e.g., USA.	T	Map to “Shipping Country” using “Field.”	Identifies the shipping country.
	Country CodeShipping country code, e.g., US.	T	Map to “Shipping Country Code” using “Field.”	Standardizes country identification.
	EmailRecipient’s email, e.g., recipient@example.com.	T	Map to “Customer Email” using “Field.”	Ensures contact information is captured.
	Full NameRecipient’s full name, e.g., Jane Smith.	T	Map to “Shipping Address Name” using “Field.”	Identifies the recipient.
	PhoneRecipient’s phone number, e.g., 555-987-6543.	T	Map to “Customer Phone” using “Field.”	Provides contact number for shipping.
	Postal CodeShipping postal code, e.g., 60601.	T	Map to “Shipping Zip” using “Field.”	Ensures accurate shipping location.
	State or ProvinceShipping state, e.g., IL.	T	Map to “Shipping State” using “Field.”	Specifies the shipping state.
eBay Order Item
	Discounted Line Item CostDiscounted price, e.g., 20.00.	N	Map to “Discounted Price” or “Don’t Map.”	Tracks discounted price if applicable.
	Discounted Line Item Cost CurrencyCurrency for discounted price, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for discounted price.
	eBay Collected Shipping ChargesShipping fees collected by eBay, e.g., 5.00.	N	Map to “Shipping Cost” using “Field.”	Includes eBay-collected shipping fees.
	eBay Collected Shipping Charges CurrencyCurrency for shipping fees, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for shipping fees.
	Gift MessageGift message, e.g., Happy Birthday!	T	Map to “Gift Message” or “Don’t Map.”	Optional for gift orders.
	Gift Recipient EmailRecipient’s email, e.g., gift@example.com.	T	“Don’t Map” or custom field.	Optional for gift recipient contact.
	Gift Sender NameSender’s name, e.g., John Doe.	T	“Don’t Map” or custom field.	Optional for gift sender identification.
	Item LocationLocation of item, e.g., Warehouse A.	T	“Don’t Map” or custom field.	Optional for item origin.
	Item Location Country CodeCountry code of item location, e.g., US.	T	“Don’t Map” or custom field.	Optional for item origin country.
	Item Location Postal CodePostal code of item location, e.g., 90210.	T	“Don’t Map” or custom field.	Optional for item origin location.
	Legacy Item IDLegacy item identifier, e.g., OLD-ITEM-123.	T	Map to “External Item ID” or “Don’t Map.”	Supports legacy systems.
	Legacy Variation IDLegacy variation identifier, e.g., VAR-456.	T	“Don’t Map” or custom field.	Optional for variation tracking.
	Line Item CostCost per unit, e.g., 25.00.	N	Map to “Line Item Price” using “Field.”	Tracks per-unit cost.
	Line Item Cost CurrencyCurrency for line item cost, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for line item cost.
	Line Item Fulfillment StatusFulfillment status of item, e.g., Shipped.	T	Map to “Line Item Status” or “Don’t Map.”	Tracks item fulfillment progress.
	Line Item IDUnique ID for line item, e.g., LI-789.	T
	Line Item IDUnique ID for line item, e.g., LI-789.	T	"Don’t Map” or custom field.	Optional for line item tracking.
	Listing Marketplace IDMarketplace ID for listing, e.g., EBAY-US.	T	“Don’t Map” or custom field.	Optional for marketplace identification.
	Purchase Marketplace IDMarketplace ID for purchase, e.g., EBAY-US.	T	“Don’t Map” or custom field.	Optional for purchase marketplace.
	QuantityQuantity purchased, e.g., 2.	N	Map to “Line Item Quantity” using “Field.”	Tracks purchased quantity.
	SKUStock Keeping Unit, e.g., ABC123.	T	Map to “Line Item SKU” using “Field.”	Matches item to Flxpoint inventory.
	Sold FormatFormat of sale, e.g., Auction.	T	“Don’t Map” or custom field.	Optional for sale format.
	TotalTotal cost for line item, e.g., 50.00.	N	Map to “Line Item Total” using “Field.”	Calculates total cost for the line item.
	Total CurrencyCurrency for line item total, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for line item total.
eBay Order Item Applied Promotion
	DescriptionPromotion description, e.g., 10% Off.	T	“Don’t Map” or custom field.	Optional for promotion details.
	DiscountDiscount amount, e.g., 5.00.	N	Map to “Discount Amount” or “Don’t Map.”	Tracks promotion discount.
	Discount CurrencyCurrency for discount, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for discount.
	Promotion IDUnique ID for promotion, e.g., PROMO-123.	T	“Don’t Map” or custom field.	Optional for promotion tracking.
eBay Order Item Delivery Cost
	Discount AmountShipping discount, e.g., 2.00.	N	Map to “Shipping Discount” or “Don’t Map.”	Tracks shipping discounts.
	Discount Amount CurrencyCurrency for shipping discount, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for discount.
	Handling CostHandling fee, e.g., 3.00.	N	Map to “Add-on Fees” using “Field.”	Includes handling fees.
	Handling Cost CurrencyCurrency for handling fee, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for handling fees.
	Import ChargesImport fees, e.g., 10.00.	N	Map to “Import Fees” or “Don’t Map.”	Tracks import charges for international orders.
	Import Charges CurrencyCurrency for import charges, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for import charges.
	Shipping CostCost of shipping, e.g., 7.00.	N	Map to “Shipping Cost” using “Field.”	Includes shipping cost for the item.
	Shipping Cost CurrencyCurrency for shipping cost, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for shipping cost.
	Shipping Intermediation FeeIntermediation fee, e.g., 1.00.	N	“Don’t Map” or custom field.	Optional for intermediation fees.
	Shipping Intermediation Fee CurrencyCurrency for intermediation fee, e.g., USD.	T	“Don’t Map” or custom field.	Optional for fee currency.
eBay Order Item Fulfillment Instructions
	Destination TimezoneTimezone of destination, e.g., PST.	T	“Don’t Map” or custom field.	Optional for delivery scheduling.
	Max Estimated Delivery DateLatest delivery date, e.g., 2025-05-25.	D	Map to “Max Delivery Date” or “Don’t Map.”	Provides delivery estimate.
	Min Estimated Delivery DateEarliest delivery date, e.g., 2025-05-22.	D	Map to “Min Delivery Date” or “Don’t Map.”	Provides delivery estimate.
	Ship By DateDate to ship by, e.g., 2025-05-21.	D	Map to “Ship By Date” or “Don’t Map.”	Ensures timely shipping.
	Source TimezoneTimezone of origin, e.g., EST.	T	“Don’t Map” or custom field.	Optional for shipping origin.
eBay Order Payment
	Payment AmountAmount paid, e.g., 55.00.	N	Map to “Payment Amount” using “Field.”	Tracks the payment amount.
	Payment Amount CurrencyCurrency for payment, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for payment.
	Payment DateDate of payment, e.g., 2025-05-20.	D	Map to “Payment Date” using “Field.”	Records when payment was made.
	Payment MethodMethod of payment, e.g., PayPal.	T	Map to “Payment Type” using “Field.”	Identifies how the buyer paid.
	Payment Reference IDTransaction ID, e.g., TXN-789.	T	Map to “Transaction ID” using “Field.”	Tracks payment transaction.
	Payment StatusStatus of payment, e.g., Completed.	T	Map to “Payment Status” using “Field.”	Tracks payment status.
eBay Order Pricing Summary
	AdjustmentPrice adjustment, e.g., -2.00.	N	“Don’t Map” or custom field.	Optional for pricing adjustments.
	Adjustment CurrencyCurrency for adjustment, e.g., USD.	T	“Don’t Map” or custom field.	Optional for adjustment currency.
	Delivery CostTotal delivery cost, e.g., 10.00.	N	Map to “Shipping Cost” using “Field.”	Includes total delivery cost.
	Delivery Cost CurrencyCurrency for delivery cost, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for delivery cost.
	Delivery DiscountDiscount on delivery, e.g., 3.00.	N	Map to “Shipping Discount” or “Don’t Map.”	Tracks delivery discounts.
	Delivery Discount CurrencyCurrency for delivery discount, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for discount.
	FeeAdditional fee, e.g., 2.00.	N	“Don’t Map” or custom field.	Optional for additional fees.
	Fee CurrencyCurrency for fee, e.g., USD.	T	“Don’t Map” or custom field.	Optional for fee currency.
	Price DiscountDiscount on price, e.g., 5.00.	N	Map to “Discount Amount” or “Don’t Map.”	Tracks price discounts.
	Price Discount CurrencyCurrency for price discount, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for discount.
	Price SubtotalSubtotal before taxes/fees, e.g., 45.00.	N	Map to “Subtotal” using “Field.”	Tracks order subtotal before taxes/fees.
	Price Subtotal CurrencyCurrency for subtotal, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for subtotal.
	TaxTax amount, e.g., 5.00.	N	Map to “Tax Amount” using “Field.”	Tracks tax for accounting purposes.
	Tax CurrencyCurrency for tax, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for tax.
	TotalFinal order total, e.g., 60.00.	N	Map to “Order Total” using “Field.”	Calculates final order total.
	Total CurrencyCurrency for order total, e.g., USD.	T	Map to “Order Currency” using “Field.”	Specifies currency for order total.
eBay Order Refund
	Refund AmountAmount refunded, e.g., 60.00.	N	Map to “Refund Amount” using “Field.”	Tracks the refunded amount.
	Refund Amount CurrencyCurrency for refund, e.g., USD.	T	Map to “Currency” or “Don’t Map.”	Specifies currency for refund.
	Refund DateDate of refund, e.g., 2025-05-20.	D	Map to “Refund Date” using “Field.”	Records when the refund was issued.
	Refund IDUnique ID for refund, e.g., REF-123.	T	“Don’t Map” or custom field.	Optional for refund tracking.
	Refund Reference IDReference ID for refund, e.g., REF-456.	T	“Don’t Map” or custom field.	Optional for refund reference.
	Refund StatusStatus of refund, e.g., Completed.	T	Map to “Refund Status” or “Don’t Map.”	Tracks refund status.

Source Data Fields

eBay Buyer Registration Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), Full Name (T), Phone (T), Postal Code (T), State or Province (T).
eBay Buyer Tax Address: City (T), Country Code (T), Postal Code (T), State or Province (T).
eBay Buyer Tax Identifier: Issuing Country (T), Tax Identifier Type (T), Taxpayer ID (T).
eBay Order: Authenticity Verification Outcome Reason (T), Authenticity Verification Status (T), Buyer Checkout Notes (T), Buyer Username (T), Cancel State (T), Cancelled Date (D), Creation Date (D), Fulfilled By (T), Last Modified Date (D), Legacy Order ID (T), Order Fulfillment Status (T), Order ID (T), Order Payment Status (T), Sales Record Reference (T), Seller ID (T), Total Due Seller (N), Total Due Seller Currency (T), Total Fee Basis Amount (N), Total Fee Basis Amount Currency (T), Total Marketplace Fee (N), Total Marketplace Fee Currency (T), eBay International Shipping Returns Managed By (T), eBay Shipping Label Provided By (T), eBay Vault Fulfillment Type (T).
eBay Order Fulfillment Appointment: Appointment End Date (D), Appointment Start Date (D), Appointment Type (T), Appointment Status (T), Appointment Window (T), Service Provider Appointment Date (D).
eBay Order Fulfillment Destination Address: Address Line 1 (T), Address Line 2 (T), City (T), Country (T), Country Code (T), Postal Code (T), State or Province (T).
eBay Order Fulfillment Instructions: Destination Timezone (T), Fulfillment Instruction Type (T), Max Estimated Delivery Date (D), Min Estimated Delivery Date (D), Pickup Merchant Location Key (T).
eBay Order Fulfillment Shipping Step: Ship To Reference ID (T), Shipping Carrier Code (T), Shipping Service Code (T).
eBay Order Fulfillment Ship To Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), Full Name (T), Phone (T), Postal Code (T), State or Province (T).
eBay Order Item: Discounted Line Item Cost (N), Discounted Line Item Cost Currency (T), eBay Collected Shipping Charges (N), eBay Collected Shipping Charges Currency (T), Gift Message (T), Gift Recipient Email (T), Gift Sender Name (T), Item Location (T), Item Location Country Code (T), Item Location Postal Code (T), Legacy Item ID (T), Legacy Variation ID (T), Line Item Cost (N), Line Item Cost Currency (T), Line Item Fulfillment Status (T), Line Item ID (T), Listing Marketplace ID (T), Purchase Marketplace ID (T), Quantity (N), SKU (T), Sold Format (T), Total (N), Total Currency (T).
eBay Order Item Applied Promotion: Description (T), Discount (N), Discount Currency (T), Promotion ID (T).
eBay Order Item Delivery Cost: Discount Amount (N), Discount Amount Currency (T), Handling Cost (N), Handling Cost Currency (T), Import Charges (N), Import Charges Currency (T), Shipping Cost (N), Shipping Cost Currency (T), Shipping Intermediation Fee (N), Shipping Intermediation Fee Currency (T).
eBay Order Item Fulfillment Instructions: Destination Timezone (T), Max Estimated Delivery Date (D), Min Estimated Delivery Date (D), Ship By Date (D), Source Timezone (T).
eBay Order Payment: Payment Amount (N), Payment Amount Currency (T), Payment Date (D), Payment Method (T), Payment Reference ID (T), Payment Status (T).
eBay Order Pricing Summary: Adjustment (N), Adjustment Currency (T), Delivery Cost (N), Delivery Cost Currency (T), Delivery Discount (N), Delivery Discount Currency (T), Fee (N), Fee Currency (T), Price Discount (N), Price Discount Currency (T), Price Subtotal (N), Price Subtotal Currency (T), Tax (N), Tax Currency (T), Total (N), Total Currency (T).
eBay Order Refund: Refund Amount (N), Refund Amount Currency (T), Refund Date (D), Refund ID (T), Refund Reference ID (T), Refund Status (T).

Mapping Simulator

Simulate mapping a field to Flxpoint:

Optimize your Get Orders process with these best practices:

Validate Mappings: Ensure critical fields like Order ID and SKU are correctly mapped.
Filter Orders: Use Fulfillment Status filtering to focus on actionable orders.
Limit Fetch Period: Set to 7 days to prevent duplicate imports.
Standardize Shipping: Use Mapping Sets for eBay shipping methods.
Monitor PII: Review PII retention settings for compliance.

Efficiency Tip: Create separate templates for domestic and international orders to streamline processing.

Common issues and solutions:

Orders Not Importing: Check Fulfillment Status filters.
Duplicate Orders: Adjust “Fetch Last X Days” to a shorter period.
Unknown Shipping Method: Verify Shipping Mappings.
Missing Buyer Details: Check PII retention settings.
Mapping Errors: Ensure required fields are mapped.

           Diagnostic Tip: Test with one order to verify mappings before importing a large batch.
        

Conclusion

With a properly configured Get Orders template, you can efficiently import eBay orders into Flxpoint. Map fields accurately, set filters, and standardize shipping methods for smooth fulfillment and inventory management. Save your configuration to start importing orders seamlessly.

Sync Orders

eBay V2 integration: Supported
eBay Legacy integration: Supported

Sync Orders: eBay Legacy & eBay v2

Introduction to Sync Orders for eBay

The Sync Orders operation keeps your eBay marketplace and Flxpoint system in perfect harmony by automatically updating order statuses and shipping details. This integration ensures customers receive accurate tracking information while saving you time on manual updates. Whether you're using eBay's Legacy Trading API or the newer v2 REST API, this integration streamlines your post-order processes and enhances the customer experience.

The Sync Orders integration connects your Flxpoint system to eBay to:

Automatically update eBay with shipping carriers, methods, and tracking numbers when orders are fulfilled in Flxpoint.
Support both partial and full shipments, allowing for staged fulfillment when necessary.
Maintain consistent order status information across both platforms.
Reduce customer inquiries by providing timely, accurate tracking information.
Eliminate manual data entry and the associated potential for errors.

eBay Legacy vs. eBay v2

There are two versions of the eBay integration available:

eBay Legacy: Uses Trading API calls to apply tracking updates to eBay.
eBay v2: Uses newer REST API calls but shows a similar workflow in Flxpoint.

Both versions accomplish the same goal—updating eBay with your shipment information—but use different underlying technologies. From your perspective in Flxpoint, the setup and operation are very similar.

The Sync Orders integration follows a clear, step-by-step process to keep eBay updated with your shipping information:

Tracking Updates: Whenever you mark an order as shipped in Flxpoint—partial or full—Sync Orders pushes the corresponding tracking number, carrier, and shipping date to eBay. The buyer can then see the status on eBay.
Post-Shipment Status: Flxpoint automatically flags that order's status as "shippedto" in your system once the sync is complete. If it's a partial shipment, only the shipped items get updated while unshipped items remain open until the next sync.
Status Synchronization: Once all items in an order have been marked as shipped, eBay updates the order status to "Shipped" or "Completed" on their platform.

Supported Features

The integration supports several key features that provide flexibility in your fulfillment process:

Partial Order Shipments: If some items in an order ship before others, you can update just those items, and eBay will show them as shipped while keeping the rest as pending.
Full Order Shipments: When an entire order ships at once, all items are updated simultaneously with the same tracking information.
Carrier & Method Mapping: Map your internal shipping carriers and methods to eBay's recognized values, ensuring accurate display on their platform.

Critical Requirements for eBay Tracking:

DO NOT use the same tracking number for different eBay orders. Each order must have a unique tracking number. Reusing tracking numbers will cause synchronization failures with eBay.
Always add carrier and shipping method information when manually adding shipments. Ensure that both the carrier (e.g., USPS, FedEx, UPS) and the shipping method (e.g., Ground, Priority Mail) are specified. Missing this information can prevent tracking from syncing correctly to eBay.

Setting up the Sync Orders integration is straightforward, with minimal configuration needed:

Basic Setup

Connect an Integration: Select either eBay Legacy or eBay v2 and provide your credentials. If you already have a channel, ensure "Sync Orders" is enabled.
Additional Settings: Typically, there are few additional configurations needed for this operation, as it primarily relies on the mapping template to determine how shipment data is transmitted to eBay.

Mapping Options

The most important aspect of configuration is the mapping template, which defines how your Flxpoint shipment data is translated to eBay's format:

Field: Maps a field from your Flxpoint shipment data directly to eBay (e.g., mapping "Shipment: Tracking Number" to eBay's "Tracking Number" field).
Value: Sets a static value for all shipments (e.g., if all your shipments use the same carrier).
Mapping Set: Translates values between systems (e.g., converting internal carrier codes to eBay's recognized carrier codes).
Rules: Applies conditional logic to determine values based on specific criteria.
Don't Map: Skips mapping for optional fields that you don't want to include.
Set to Empty: Clears a field in eBay's system (rarely used but can be helpful in specific scenarios).

                                               Recommended Configuration: At minimum, you should map:
                                              
                                            Tracking Number (required)
                                        
                                            Carrier (required)
                                        
                                            Shipped At (recommended)
                                        
                                              For partial shipments, also map SKU and Quantity at the line item level.

Follow these steps to get the Sync Orders integration up and running:

1 Connect an Integration: In Flxpoint, navigate to Channels and select either eBay Legacy or eBay v2. Provide your eBay credentials if you haven't already set up a channel.
2 Enable Sync Orders: Make sure the "Sync Orders" operation is enabled for your eBay channel.
3 Access Mapping Dashboard: Click the three dots (⋮) menu on the Sync Orders tile, then select "Manage Mapping" to open the field mapping interface.
4 Configure Shipment Mappings: Set up how your Flxpoint shipment data maps to eBay's fields:
- Map "Shipment: Carrier" to eBay's Carrier field
- Map "Shipment: Method" to eBay's Method field
- Map "Shipment: Shipped At" to eBay's Shipped At field
- Map "Shipment: Tracking Number" to eBay's Tracking Number field
5 Configure Shipment Item Mappings (for partial shipments):
- Map "Shipment Item: SKU" to eBay's Shipment Item SKU field
- Map "Shipment Item: Quantity" to eBay's Shipment Item Quantity field
6 Save Mapping: Click the "Save Mapping" button to store your field mapping configuration.
7 Set Schedule (Optional): Click the three dots (⋮) menu again and select "Adjust Schedule" to set how frequently the integration should check for new shipment information to push to eBay.
8 Run Manual Test: Process a test shipment in Flxpoint, then click "Run Sync" from the menu to manually trigger the integration and push the shipment data to eBay.

Important: After setting up your integration, verify that your first few shipments properly update in eBay by checking your eBay Seller Hub. Confirm that tracking numbers appear correctly and that order statuses update as expected.

The Mapping Template is where you define how your Flxpoint shipment data connects to eBay's required fields. This is the most critical component of the integration, as it determines what information gets sent to eBay and how it's formatted.

Shipment Fields

These fields apply to the overall shipment and are used by eBay to track packages and update order status:

Flxpoint Field	Maps To	Purpose	Recommended Mapping
Carrier	eBay Shipment: Carrier	eBay's recognized shipping carrier	"Shipment → Carrier" or static Value
Method	eBay Shipment: Method	eBay's shipping service name	Optional - "Shipment → Method" or static Value
Shipped At	eBay Shipment: Shipped At	Date/time the items were shipped	"Shipment → Shipped At"
Tracking Number	eBay Shipment: Tracking Number	The unique tracking ID	"Shipment → Tracking Number"

Shipment Item Fields

These fields are used for partial shipments to specify which items and quantities are being shipped:

Flxpoint Field	Maps To	Purpose	Recommended Mapping
SKU	eBay Shipment Item: SKU	Identifies which line item is being shipped	"Shipment Item → SKU"
Quantity	eBay Shipment Item: Quantity	Specifies how many units of this SKU are shipping	"Shipment Item → Quantity"

Mapping Modes

For each field, you can choose different mapping modes:

Mapping Mode	Purpose	Example Use Case
Field	Maps a field from Flxpoint directly to eBay	Mapping "Shipment: Tracking Number" to eBay's "Tracking Number"
Value	Uses a static text or date value	Setting "Method" to always be "Ground"
Mapping Set	Translates values between systems	Converting internal carrier "UPSGround" to eBay's "UPS Ground"
Rules	Applies conditional logic	If carrier is DHL, set "Carrier Code" to "DHLExpress"
Don't Map	Skips mapping for optional fields	When you don't need to specify a shipping method
Set to Empty	Clears a field in eBay's system	Removing a previously sent tracking number (rare)

Carrier Mapping Tip: eBay recognizes specific carrier codes. If your internal carrier names don't match eBay's expected format, use a Mapping Set to translate them. For example, map your internal "USPS" to eBay's recognized "USPS" code, or "FedEx Ground" to eBay's "FedEx".

The Sync Orders integration supports both partial and full shipments, giving you flexibility in your fulfillment process.

Full Shipments

When an entire order ships at once, the process is straightforward:

Mark the entire order as shipped in Flxpoint with a single tracking number
The integration sends the tracking number, carrier, and ship date to eBay
eBay updates the order status to "Shipped" or "Completed"
The customer sees tracking information for their entire order

Partial Shipments

For orders where items ship separately, you need to provide additional information:

Mark specific items as shipped in Flxpoint, indicating quantity for each
The integration sends tracking information along with SKU and quantity details
eBay marks those specific items as shipped while keeping others as pending
When remaining items ship, repeat the process with new tracking information
Once all items have shipped, eBay updates the overall order status

                                               How Partial Shipments Work: If a customer orders 3 units of SKU-A and 2 units of SKU-B, but only 2 units of SKU-A and 1 unit of SKU-B are ready to ship, you can:
                                              
                                            Create a shipment in Flxpoint with tracking number "123456" for 2 units of SKU-A and 1 unit of SKU-B
                                        
                                            The integration sends this to eBay, marking those specific quantities as shipped
                                        
                                            Later, create another shipment with tracking number "789012" for the remaining 1 unit of SKU-A and 1 unit of SKU-B
                                        
                                            The integration sends this second update to eBay, completing the order

Important for Partial Shipments: Each shipment must use a unique tracking number. Never reuse the same tracking number for different shipments or orders, as this will cause synchronization failures with eBay.

While the setup and operation are similar, there are some differences between eBay Legacy and eBay v2 integrations.

eBay Legacy

eBay v2

eBay Legacy Specifics

API Technology: Uses eBay's Trading API for shipment updates
Order Identification: Uses the legacy "OrderID" format to identify orders
Partial Shipments: Provides item or transaction IDs and shipped quantities
Authentication: Uses Auth Token for API access
Legacy Compatibility: Better for older eBay accounts or specific legacy requirements

Legacy Note: For eBay Legacy, the integration automatically handles the conversion between your Flxpoint data and eBay's Trading API format. Even though the underlying API calls are different, the mapping process in Flxpoint remains straightforward and user-friendly.

eBay v2 Specifics

API Technology: Uses eBay's newer REST API calls for better performance and reliability
Modern Architecture: Offers improved scalability and future compatibility
Identification: Uses references to "inventoryItemGroup" or "offer IDs" under the hood
Authentication: Uses OAuth tokens for more secure API access
Recommended For: New eBay integrations or migrating from legacy systems

v2 Note: Despite the technical differences in the underlying API, the Flxpoint interface for eBay v2 is similar to Legacy. You'll map the same basic fields (Carrier, Method, Tracking Number, etc.) regardless of which version you're using.

                                               Which Version Should I Use? If you're setting up a new integration, eBay v2 is generally recommended as it uses the newer API architecture. However, if you have an existing Legacy implementation or specific requirements tied to the Trading API, the Legacy integration remains fully supported.
                                            
                                

Follow these best practices to ensure smooth operation of your eBay Sync Orders integration:

Integration Setup

Complete Field Mapping: Always map all required fields (Carrier, Tracking Number) and recommended fields (Shipped At, Method) for the best customer experience.
Test Before Going Live: Process a test shipment and verify it appears correctly in your eBay Seller Hub before relying on the integration for all orders.
Set Appropriate Sync Schedule: Configure the integration to run frequently enough to keep eBay updated in a timely manner (typically hourly or several times per day).

Shipment Operations

Use Unique Tracking Numbers: Never reuse tracking numbers across different orders or shipments, as this causes synchronization failures with eBay.
Include All Required Information: Always provide both carrier and shipping method when creating shipments to ensure tracking displays correctly in eBay.
Verify Carrier Codes: Ensure your internal carrier names map correctly to eBay's recognized carrier codes, using Mapping Sets if necessary.
Monitor Partial Shipments: For orders with multiple shipments, verify that all items eventually show as shipped in eBay.

Common Pitfalls to Avoid

Missing Carrier Information: Failing to specify a carrier will prevent eBay from displaying tracking correctly.
Duplicate Tracking Numbers: Reusing tracking numbers across different orders will cause sync failures.
Incorrect Mapping: Mapping fields incorrectly (e.g., mapping a date field to a carrier) will result in invalid updates.
Ignoring Partial Shipment Fields: For partial shipments, forgetting to map SKU and Quantity will cause the entire order to be marked as shipped.

Tracking Number Requirements:

Each eBay order must have its own unique tracking number(s)
Never reuse tracking numbers across different orders
Always include carrier information with tracking numbers
For split shipments, use different tracking numbers for each shipment

If you encounter issues with the Sync Orders integration, here are some common problems and solutions:

Common Issues

Problem	Possible Causes	Solution
Tracking not appearing in eBay	Missing carrier information or incorrect mapping	Verify that both carrier and tracking number are mapped correctly and include both in all shipments
Sync error: "Duplicate tracking number"	Tracking number already used for another order	Use unique tracking numbers for each order and shipment
Only some items in an order showing as shipped	Incorrect partial shipment configuration	Check SKU and Quantity mappings for partial shipments
Authentication errors	Expired or invalid eBay credentials	Refresh your eBay authorization or check account settings
Order not found errors	Order ID mismatch between systems	Verify the order exists in eBay and check order ID format

Diagnostic Steps

Check Logs: Review the integration logs for specific error messages by clicking "View Logs" from the Sync Orders menu.
Verify Mappings: Confirm all required fields are correctly mapped in the Mapping Template.
Test Manual Update: Try updating a single order manually in eBay to see if it succeeds.
Check eBay Account: Verify your eBay seller account is in good standing with no restrictions.
Refresh Authorization: For eBay v2, try refreshing the OAuth token by reconnecting the integration.

Support Tip: If you continue to experience issues after trying these troubleshooting steps, contact support with:

The specific error message from your logs
The eBay order ID that's having problems
Screenshots of your mapping configuration
Details about the shipment you're trying to sync

This information will help support diagnose and resolve the issue more quickly.

Conclusion

The eBay Sync Orders integration provides a seamless way to keep your eBay marketplace and Flxpoint system synchronized with accurate shipping and tracking information. By properly configuring the field mappings and following best practices—particularly regarding unique tracking numbers and complete carrier information—you can provide your customers with a superior post-purchase experience while saving time on manual updates. Whether you choose the Legacy or v2 version, the integration streamlines your fulfillment workflow and helps maintain your reputation as a reliable eBay seller.

Flxpoint Knowledge

How to Connect

Listing Operations

Import Listings

Sync & Link Listings

Publish Listings

Order Operations

Get Orders

Sync Orders

Related Articles