Amazon FBA

Amazon FBA (Fulfillment by Amazon) is a service that allows you to store your products in Amazon’s fulfillment centers, with Amazon handling picking, packing, shipping, and customer service. By integrating Amazon FBA as a source in Flxpoint, you can leverage Amazon’s logistics network for order fulfillment while syncing product data and inventory levels directly in Flxpoint.

 

How To Connect

📋 Phase 1: Create Your Amazon FBA Source +
Create Source in Flxpoint
Log into your Flxpoint account, go to the Sources tab, and click + Add Source.
Source Details
Name it Amazon FBA, select the appropriate source type (e.g., Vendor Warehouse), and optionally assign a vendor for better reporting. Click Save & Next.
Tip: Assigning a vendor helps with reporting and organization.
Choose Integrations to Configure Later
In the Integrations section, you can set up:
  • Get Inventory (Primary)
  • Send Fulfillment Requests
  • Get Shipments
Note: Enable only what you need now; you can add others later.
🔐 Phase 2: Set Up Connection (SP-API) +
Gather Credentials
You will need your SP-API Refresh Token, Seller ID, and Marketplace.
  • Sign in to your Amazon Seller Central and obtain SP-API access.
  • Locate or generate your Refresh Token and confirm your Seller ID.
Important: Keep these credentials secure.
Create New Connection
In Flxpoint, open New Connection and enter:
  • Connection Name: “Amazon FBA Connection”
  • SP-API Refresh Token
  • Seller ID
  • Marketplace
Click Test Connection, then Save Connection.
Tip: If the test fails, recheck the token scope and marketplace.
🛒 Phase 3: Configure Order & Shipment Integrations +
Enable Send Fulfillment Requests / Get Shipments
Use the connection from Phase 2:
  • Send Fulfillment Requests: Map order fields (Customer, Address, Items) to ensure accurate transmission.
  • Get Shipments: Map shipment fields like Tracking Number, Carrier, and Shipment Date.
Automation Settings
  • Toggle Automatically Send Fulfillment requests ON if you want automatic order submission.
  • Set any additional rules (e.g., order minimums or filters).
✅ Phase 4: Mapping & Activation +
Create Field Mapping (Inventory)
Map essential fields like SKU, Price, Quantity, and Description. Add transformations as needed (e.g., markup, quantity buffers).
Master SKU Mapping
Configure Master SKU mapping (Inventory SKU → Master SKU). Consider a prefix (e.g., FBA-) for quick identification.
Activate & Verify
Click Save and Complete. Monitor runs in Integrations under Fulfillment Sources.
Next: The first sync can take time depending on catalog size.

 

Product Operations

Get Inventory (Primary)

Supported | Amazon FBA — Get Inventory (Primary)
Introduction
The Get Inventory (Primary) job (listed as GIP) imports Amazon product and stock data into Flxpoint’s Global Inventory Pool. It keeps FBA quantities current and can optionally add FBM stock depending on your configuration.
Note: “GIP” = the import job. The Global Inventory Pool is where the data is stored after the job runs.
  • Import core Amazon data (SKU, Title, Description, Brand, optional category levels).
  • Keep FBA stock in sync; optionally include FBM stock.
  • Use mapping templates + post-mapping workflows (e.g., “Do Not Import Deleted SKUs”).
  • Provide a reliable inventory baseline for all downstream channels.

Create a new Amazon connection in your Source:

  • 1Connection Name (e.g., Amazon FBA)
  • 2Marketplace ID (select your region)
  • 3Refresh Token (created via OAuth2 after saving)
  • 4Selling Partner ID (your Amazon Seller ID)
Save → authorize the Flxpoint app in Seller Central → return → Test Connection.
  • Include FBM Quantity? — If ON, final quantity = FBA + FBM. If OFF, only FBA is counted.
  • Fetch Missing Inventory from FBA APIAdvanced flag (per store). When enabled, Flxpoint will query the FBA Inventory API for SKUs missing in the reports before defaulting to 0. Gradual global rollout.
  • Archive/Un-Archive Inventory — Not supported for this job; leave OFF.
Marketplace coverage: The fallback mechanism applies to US and CA marketplaces.

Map at minimum:

Flxpoint Field Amazon Field Why It Matters
SKU seller-sku Primary unique key.
Title title Product name for listings.
Description description Optional but useful.
Brand brand Standardized catalog labeling.
Quantity Quantity Available (SELLABLE) Stock level; optionally add FBM.
Categories category 1–3 Helpful for downstream mapping.
Image URL Not provided Amazon reports don’t include image URLs.
Workflow rules: Enable “Do Not Import Deleted SKUs” or “Do Not Import Excluded SKUs” as needed.
  • 1Token — Use the Refresh Token to get an access token (~3600s).
  • 2Reports — Request:
    • GET_MERCHANT_LISTINGS_ALL_DATA (Product Listings Report)
    • GET_AFN_INVENTORY_DATA (AFN Inventory Report)
  • 3Fallback (when enabled) — If a SKU is missing in both reports, Flxpoint will query the FBA Inventory API (supports batch lookups up to ~50 SKUs) before defaulting quantity to 0.
  • 4Persist — Process data and store raw/parsed copies; update the Global Inventory Pool.
Example: SKU P-V3-FBA didn’t appear in amazon_afn_inventory_report. With the fallback flag ON, Flxpoint queried the FBA Inventory API and successfully retrieved its quantity.
Quantity Logic Clarification
Normal process (without fallback):
1) Pull from amazon_afn_inventory_report → 2) If missing, check amazon_all_listings_report → 3) If still missing, quantity = 0.

Updated process (with fallback flag):
If missing in both reports → query FBA Inventory API → if still not found, quantity = 0.
  • Mismatch checks: verify seller-sku, Quantity Available, and Warehouse-Condition-code in AFN report; only SELLABLE counts are used. If multiple SELLABLE rows exist for the same SKU, values are summed.
  • FBM included? If the “Include FBM Quantity” toggle is ON, final quantity = FBA SELLABLE + FBM.
Why not always use the API? The API is resource-intensive and limited to batch lookups (up to ~50 SKUs), while reports return all SKUs at once. For performance and cost, the API is used selectively as a fallback.
Capability Status Notes
Generic Pricing Supported Price/Cost from reports.
Quantity Supported FBA with optional FBM; fallback API for missing SKUs (US & CA).
Custom Fields / Variations / Client Pricing Not Supported Not in Amazon reports.
Images / Weights / Dimensions / Categories Not Supported Not provided by reports.
Delta Feed Not Supported Runs as a full feed.
Archive Support Not Supported Leave OFF.

Once Connected → Configured → Mapped, click Save and Complete, then enable a schedule (times in UTC).

 
 


Order Operations

Send Fulfillment Requests

Supported | Amazon FBA — Send Fulfillment Requests
Introduction
Send Fulfillment Requests (SFR) submits orders from Flxpoint to Amazon MCF via the Selling Partner API (SP-API). You control when requests go out, map shipping methods, and receive processing feedback automatically.
  • Transmit customer shipping details and line items for Amazon to fulfill (MCF).
  • Map your internal shipping methods (e.g., “Standard”, “Expedited”, “Priority”) to Amazon’s expected codes.
  • Receive accept/reject processing results back to Flxpoint for visibility.

In your Source, choose Amazon and select your Amazon FBA OAuth2 connection (the same store used for inventory).

  • 1Confirm the connection tests successfully.
  • 2Click Save and Proceed to continue to configuration.
  • Hold for X Hours — Delay sending new orders for the specified hours (useful for manual QA before release).
  • Only Send During Business Hours — Restrict dispatch to business hours in your account’s timezone.
Tip: Use a short hold (e.g., 2–4 hours) to catch fraud checks or address fixes without blocking all-day.

At minimum, map these fields before completing setup:

Flxpoint Field Where It Comes From Notes
Fulfillment Request Number Order/FR header Sent to Amazon for traceability (idempotency helper).
Shipping Method / Code Mapping template Map to Amazon codes (e.g., Standard, Expedited, Priority).
Ship To: Name, Address 1/2, City, State/Code, Postal, Country/Code, Email, Phone Order shipping address Amazon validates; ensure country/state codes are ISO-compatible.
Item SKU Line item Must match seller-sku in Amazon.
Item Quantity Line item Integer > 0.
Item Title / UPC (optional) Line item Helpful for debugging; not required by Amazon.
For a field-by-field view of the template UI and address field grouping, see the “Send Fulfillment Requests” mapping screen. :contentReference[oaicite:0]{index=0}
  • 1Authenticate — Generate a new access token if the previous one expired.
  • 2Create Feed Document — Call /feeds/2021-06-30/documents with request type FULFILLMENT_ORDER_REQUEST.
  • 3Build & Upload — Construct the SFR payload (XML) and upload to the returned feedDocumentId/feedURL.
  • 4Submit Feed — Create the feed pointing to the uploaded document.
  • 5Processing Results — Poll/receive processing report; Flxpoint records accept/fail for each request.
Example mapping: “Standard” → Standard, “Expedited” → Expedited, “Priority” → Priority.
Capability Status Notes
Fulfillment Request Number Supported FR# in Flxpoint is sent to Amazon.
FR Item Association Supported Each SKU/qty is included in the SFR payload.
Auto Acknowledgements Supported Processing report indicates accept/failure.
Shipping Selection Supported Codes mapped via template (Standard/Expedited/Priority).
Customer Association Not Supported Customer linkage not transmitted.
Custom Fields Not Supported SP-API feed doesn’t include arbitrary custom data.
Attachments Not Supported No file attachments in the feed.
  • Feed rejected? Check required address fields & ISO country/state codes. PO Boxes may be restricted for some methods.
  • SKU not found? Ensure FR item SKU matches the Amazon seller-sku in your FBA catalog.
  • Method mismatch? Verify your mapping template’s shipping code values match Amazon’s expected labels.
  • Stuck in processing? Review last processing report; re-submit only after resolving validation errors to avoid duplicates. Use FR# for idempotency.
Address note: Some destinations require a “Non-City” field (district/province) when city is not applicable; map accordingly if present.

After you’re Connected → Configured → Mapped, click Save and Complete. You can then enable scheduling so SFR runs automatically (notifications are sent each run; schedules use UTC by default). Combine with Hold for X Hours and Only Send During Business Hours for a safe, predictable dispatch cadence.

 
 

Get Shipments

Supported | Amazon FBA — Get Shipments
Introduction
The Get Shipments job pulls shipment confirmations from Amazon FBA into Flxpoint. Use it to capture tracking, carrier/method, shipped quantities (including partials), and keep orders in sync post-fulfillment.
  • Import shipment events for recent orders fulfilled by Amazon (MCF).
  • Attach tracking numbers, carrier, and service level to your orders.
  • Support partial shipments and line-level associations via SKU.
Runs are typically scheduled shortly after Send Fulfillment Requests so tracking updates flow back quickly.

In your Source, select Amazon and use the same Amazon FBA (OAuth2) connection you use for SFR/GIP.

  • 1Verify the connection passes Test Connection.
  • 2Click Save and Proceed to configure settings.
  • Get Shipments Within Last X Days — Lookback window for fetching shipments (e.g., 15 days).
Tip: Choose a window that covers your typical fulfillment + customer delivery timeframe. If you occasionally miss runs, temporarily increase X to backfill.

Map these fields to ensure shipments attach cleanly to orders and items:

Flxpoint Field Amazon/Report Field Notes
Order/FR Number order-id / fulfillment request reference Links shipment to the correct order.
SKU seller-sku Item association is by SKU.
Shipped Quantity quantity Supports partials across multiple shipments.
Carrier carrier As supplied by Amazon.
Service Level shipServiceLevel Standard / Expedited / Priority, etc.
Tracking Number tracking-number Primary tracking identifier.
Ship Date ship-date UTC timestamp; useful for SLA reporting.
  • 1Authenticate — Generate a new access token if the previous one expired.
  • 2Request Report — Fetch shipments using report type GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL within your lookback window.
  • 3Process — Parse shipments, associate to orders and SKUs, persist tracking + service level.
Capability Status Notes
Carrier & Methods Supported shipServiceLevel available from the platform.
Shipment Item Association Supported Items are linked by SKU.
Partial Shipments Supported Multiple shipments per order are handled.
Invoice Information Not Supported Invoice fields aren’t provided in this report.
Custom Fields (CFs) Not Supported Arbitrary custom fields aren’t ingested.
Lookback note: Only shipments inside the configured Last X Days window are fetched each run.
  • Missing tracking? Verify the shipment fell within your lookback window and the order’s SKUs match your catalog.
  • Wrong carrier/method? Check the incoming shipServiceLevel values; they come from Amazon’s data.
  • Partial not reflected? Confirm multiple shipment rows exist for the order and that each row’s SKU matches exactly.
Backfill tip: Temporarily increase Last X Days (e.g., from 15 → 30) to recover older shipments, then set it back.

After you’re Connected → Configured → Mapped, click Save and Complete. Enable scheduling so the job runs automatically (times are in UTC). Pair with your Send Fulfillment Requests cadence so tracking arrives shortly after orders are submitted.