• 1Open the channel: Go to Sales Channels → BigCommerce → Integrations and choose Import Listings.
• 2Confirm connection: Make sure your BigCommerce connection shows as Connected (OAuth or API Account). If needed, connect it from the channel’s Connect step first.
  Tip: If connecting via API Account, verify Store Hash, Client ID/Secret, and Access Token are correct and scoped for Catalog read.
• 3Configure Import options:
  • Default Listing Status: Optionally create as Paused so you can review data before taking other actions.
  • Import Scope: Bring in Products with Variants, Images, Categories, and Brand.
  • Master SKU guidance: Decide how you’ll identify items in Flxpoint later (e.g., using the BigCommerce SKU). This import does not define a mapping template.
• 4Run Import: Click Run to execute now. Scheduling is not available for Import Listings — re-run manually whenever you need to refresh.

• Progress indicators for brands, categories, products, and variants.
• Counts of created vs. updated items after completion.
• Links to resulting Listings so you can review titles, images, category paths, and brand.

Reference of common fields that Import Listings brings from BigCommerce. Availability depends on your store data.

BigCommerce Field	Description	Example	Notes
Name	Product title	“Luxury Toy Set”	Shown on parent product.
SKU	Primary identifier	TOY-001	Used for later linking/matching.
Description	Long/HTML description	“Fun educational toy…”	Sanitized to plain/HTML as supported.
Price	Base/List price	19.99	Imported for reference; not sent back by this job.
Images	Product image URLs	https://…/toy.jpg	Max 8 MB per file on publish at channel; keep originals under that size.
Categories	Category path(s)	Toys > Educational	Multi-level paths are preserved.
Brand	Brand name	Acme	If set on the product.
Weight/Dimensions	Physical attributes	2.5 / 10×12×15	If present on product/variant.

BigCommerce Field	Description	Example	Notes
Variant SKU	Child identifier	TOY-BLUE-001	Critical for later linking.
Variant Price	Per-variant price	21.99	Imported for reference.
Inventory Level	Stock quantity	50	If managed per variant.
UPC/Barcode	Global identifier	123456789013	Useful as secondary match key.
Variant Image	Per-variant image URL	https://…/toy-blue.jpg	Keep file size < 8 MB.
Options (name/value)	Option label & value	Color: Blue	See duplicate-name note in FAQs.

• Connection shows Connected before running Import.
• SKU values are unique and present on products/variants you expect to manage.
• Images you plan to later publish are < 8 MB each to avoid channel errors.
• You understand this job is manual-only; re-run when you need a refresh.

• “name: The product name is a duplicate” (publishing later): Happens when a single parent/variant structure uses the same title on parent and variant and has option name/value present.
  Fix options: (A) remove the option name/value on the standalone item, or (B) make the parent title different from the variant title.
• Images rejected for size: Reduce file size below 8 MB and retry.
• Nothing imported: Confirm catalog permissions on your BigCommerce API/OAuth app and that products are not filtered out by status.
• Rate-limit/timeout: Run in smaller batches if filters are available; retry after a short interval.

Feature	Availability	Notes
Scheduling	Not available	Import Listings runs manually only.
Creates/Updates	Supported	Brings products/variants into Flxpoint (does not publish to channel).
Images	Imported	Image URLs referenced from BigCommerce; keep each file < 8 MB if you plan to publish later.
Categories & Brand	Imported	Preserves category path(s) and brand if present.
Mapping Template	Not used	Replace any prior “Mapping Template Details” references with this Fields Imported table.

• 1Open Sync & Link: Go to Sales Channels → BigCommerce → Integrations and choose Sync Listings.
• 2Confirm connection: Ensure the BigCommerce connection is Connected (OAuth/app install or API account with Catalog scope).
  Tip: If you recently reinstalled the app or rotated API creds, click Test Connection before proceeding.
• 3Configure Settings:
  • Linking Priority — add rows in the order you want us to try (e.g., Listing Variant → SKU ↔ BigCommerce Variant → SKU; then UPC, GTIN, MPN as fallbacks).
  • Visibility Controls — choose behaviors for out-of-stock (hide, keep accessible, redirect, or do nothing).
  • Scheduling — optional; enable a cadence (e.g., hourly/daily) if you want automation.
• 4Select a Mapping Template: Pick your Sync Listings template to specify which fields we send (Quantity, Price, etc.). Save, then Run Sync or let the schedule take over.

• Wizard steps: Connect, Configure, Mapping Template — each checks off when complete.
• Linking summary after a run (linked, not found, conflicts).
• Sync results for price/quantity updates and visibility actions.

Template	Use Case	What it Covers	Availability
BigCommerce Sync Listings 1	Keep price/qty in sync	Maps List Price → Price, Quantity → Inventory Level, SKU → SKU	Available

How your Flxpoint listing fields flow to BigCommerce.

Flxpoint Field (From)	BigCommerce Variant Field (To)	Type	Required?	Notes
Listing Variant → Quantity	Inventory Level	Number	Yes	Updates variant stock level.
Listing Variant → List Price	Price	Number	Recommended	Use rules for markups/rounding.
Listing Variant → Sale Price	Sale Price	Number	Optional	Leave blank if you don’t run sales in BigCommerce.
Listing Variant → MSRP	Retail Price (MSRP)	Number	Optional	Reference/compare-at price.
Listing Variant → SKU	SKU	Text	Recommended	Primary match key for Linking Priority.
Listing Variant → Availability Description	Availability Description	Text	Optional	Customer-facing availability note.

Rule	Type	When it Helps	What it Does
Markup price by %	Number	Create selling price from cost/list	Applies a % increase and can round (e.g., .99).
Clamp min/max quantity	Number	Prevent over/under-listing	Forces sent qty within a safe range (e.g., 1–50).
When SKU starts with … then set value	String	Account for vendor prefixes	Outputs different values or flags by pattern.

Utility	Availability	How You Might Use It
Mapping Sets	Optional — available	Combine inputs (base price + fee) into one output.
Lists	Optional — available	Reusable lists (approved brands, restricted SKUs).
Builders	Optional — available	Create custom outputs if your workflow needs them.

• BigCommerce connection is authorized and saved.
• Linking Priority includes at least one reliable pair (usually SKU ↔ SKU).
• A Sync Listings mapping template is selected and saved.
• Scheduling is enabled if you want automation; otherwise run manually.

• Nothing linked — Review Linking Priority; start with SKU ↔ SKU. Make sure your BigCommerce variants actually have SKUs.
• Quantity didn’t change — Confirm template maps Quantity → Inventory Level and that the variant is inventory-tracked in BigCommerce.
• Price not updating — Verify List Price → Price (and optionally Sale Price) is mapped; check for other apps overriding price.
• API throttling — BigCommerce may rate-limit. Space your schedule (e.g., hourly) and reduce batch size if available.
• Publishing errors seen later — If you also use Publish, note BigCommerce rejects images > 8 MB. Reduce file size before publishing.
• Duplicate name error on publish — “name: The product name is a duplicate” often occurs when a single parent/variant uses identical titles with option name/values. Fix by removing the option on the standalone item or making the parent title different from the variant title.

Feature	Availability	What to Expect
Linking	Supported	SKU first; UPC/GTIN/MPN as fallbacks.
Quantity	Supported	Updates variant Inventory Level.
Price / Sale / Retail	Supported	Maps List→Price, Sale→Sale Price, MSRP→Retail Price.
Visibility	Supported	Hide/keep accessible/redirect/do nothing based on your settings.
Delisting	Supported	Removes items from sale; re-publish to restore.
Scheduling	Supported	Run on demand or enable a recurring schedule.

• 1Open Publish Listings: Go to Sales Channels → BigCommerce → Integrations and choose Publish Listings.
• 2Confirm connection: Ensure the BigCommerce connection is Connected (OAuth/app install with Catalog permissions).
  Tip: If you rotated API credentials or reinstalled the app, click Test Connection first.
• 3Configure Settings:
  • Title limit (≤ 250) — Truncate or fail product.
  • Attribute limit (≤ 250) — Truncate, skip custom field, or fail product.
  • Overwrite — Refresh complete product data on update (optional).
  • Parent Images Direct Copy — Choose which parent/variant images to copy.
  • Scheduling — Optional; enable a cadence (e.g., hourly/daily).
• 4Define a Mapping Template: Select your Publish Listings template (parent + variant fields). Save, then Run or let the schedule take over.

• Wizard steps: Connect, Configure, Mapping Template — each checks off when complete.
• Publish results: created, updated, skipped, and any validation errors.

Template	Use Case	What it Covers	Availability
BigCommerce Publish Listings 1	Create/Update products	Parent (Name, Brand, Categories, Images, Description) + Variant (SKU, Price, GTIN/MPN/UPC, Weight/Dimensions)	Available

Flxpoint Parent Field	BigCommerce Product Field	Required?	Notes
Title	Name	Yes	≤ 250 chars; use truncation setting if needed.
Brand	Brand	Optional	Created if missing.
Category 1–3	Categories	Optional	Up to 3 levels; created if missing.
Description (HTML)	Description	Optional	Sanitize HTML if copying from external sources.
Parent SKU	SKU	Optional	Useful when no variants.
Images (URLs)	Images	Optional	Each ≤ 8 MB; controlled by “Parent Images Direct Copy.”
Type	Type	Yes	physical/digital.
Price	Price	Yes	Base product price.
Weight (kg)	Weight	Yes (physical)	Needed for shipping rates.
Custom Fields	Custom Fields	Optional	Limit fields to ≤ 250 chars (per setting).

Flxpoint Variant Field	BigCommerce Variant Field	Required?	Notes
SKU	Variant SKU	Recommended	Primary identifier for updates.
List Price	Price	Recommended	Use rules for markups/rounding.
Sale Price	Sale Price	Optional	Leave blank if not running promotions.
MSRP	Retail Price	Optional	Compare-at price.
UPC / GTIN / MPN	UPC / GTIN / MPN	Optional	Helpful for marketplace feeds and audits.
Weight / Length / Width / Height	Weight / L / W / H	Weight required (physical)	Dimensions in cm; weight in kg.
Variant Image	Image	Optional	≤ 8 MB.
Availability Description	Availability Description	Optional	Customer-facing text.
Option Name/Value	Options	Optional	Each value ≤ 250 chars.

• Connection shows Connected and passes Test Connection.
• Template maps required fields: Name, Type, Weight (physical), Price.
• Title/attribute clamp settings align with your data lengths.
• Images are ≤ 8 MB each.
• Variants ≤ 250 per product.

• “name: The product name is a duplicate” — Occurs when a single parent/variant structure uses the same title on parent and variant and has option name/value present.
  Fix options: (A) remove the option name/value on the standalone item, or (B) make the parent title different from the variant title.
• Images > 8 MB — BigCommerce rejects large files. Compress each image below 8 MB (prefer JPG/WEBP) and retry.
• “Missing required field” — Map Name/Type/Weight/Price on the template; weight is mandatory for physical items.
• Option value too long — Keep option names/values ≤ 250 chars.
• Brand/Category not found — Enable create-on-missing via your mapping (Brand/Categories will be created).
• Didn’t overwrite fields — Enable Overwrite in settings to refresh all product data.
• Rate limiting — Space schedules (e.g., hourly) and reduce batch sizes if available.

Feature	Availability	What to Expect
Create Categories/Brands	Supported	Auto-creates when missing.
Variants per product	Up to 250	Publish will skip extras beyond the limit.
Images	Supported	≤ 8 MB each; “Parent Images Direct Copy” controls behavior.
Overwrite	Optional	Refreshes full product payload on update.
Scheduling	Supported	Run on demand or via recurring schedule.

• 1Add Get Orders: Go to Sales Channels → BigCommerce → Integrations and choose Get Orders. Ensure the connection shows Connected.
• 2Configure core settings:
  • Order Status — select one or more (e.g., Incomplete, Pending, Awaiting Payment).
  • Time Frame — restrict by created date (e.g., last 7–14 days).
  • PII Retention — choose how long to retain personal data (e.g., 30/60/90 days or indefinitely).
  • Scheduling — optional cadence (e.g., hourly/daily) or run on demand.
• 3Optional features:
  • Import FFL Details — pulls FFL info from Order Comments when present.
  • Multiple Shipping Addresses — line items can carry unique ship-to data.
  • Currency — use mapping rules to normalize to your base currency if needed.
• 4Create a Mapping Template: open Templates → Get Orders, map Billing/Shipping/Line Items/Order fields (see next section), Save, then Run.

• Progress by pages/batches (up to 50 orders per page).
• Results with imported/updated counts and any validation errors.

Template	Use Case	What it Covers	Availability
BigCommerce Get Orders 1	Import orders	Billing & Shipping (incl. State Code), Line Items (SKU/Qty/Prices), Order totals/notes/status	Available

BigCommerce Field	Maps To	Example	Purpose	Status
First Name	Billing - First Name	John	Buyer name	Optional
Last Name	Billing - Last Name	Doe	Buyer name	Optional
Email	Billing - Email	john@example.com	Contact	Optional
City	Billing - City	San Francisco	City	Optional
State	Billing - State	California	State name	Optional
State Code	Billing - State Code	CA	Two-letter code	Recommended
Country Iso2	Billing - Country Code	US	Country code	Optional
Street Address 1/2	Billing - Street 1/2	123 Main / Apt 4B	Address	Optional
Zip	Billing - Postal Code	94105	Postal code	Optional

BigCommerce Field	Maps To	Example	Purpose	Status
First Name / Last Name	Shipping - Name	Jane Smith	Recipient	Optional
Shipping Method	Shipping - Method	Standard Shipping	Carrier/method	Optional
City	Shipping - City	Los Angeles	City	Optional
State	Shipping - State	California	State name	Optional
State Code	Shipping - State Code	CA	Two-letter code	Recommended
Country Iso2	Shipping - Country Code	US	Country code	Optional
Street Address 1/2	Shipping - Street 1/2	456 Oak / Ste 200	Address	Optional
Zip	Shipping - Postal Code	90001	Postal code	Optional

BigCommerce Field	Maps To	Example	Purpose	Status
SKU	Line - SKU	PROD-001	Item identifier	Required
Quantity	Line - Quantity	2	Ordered units	Required
Price Ex/Inc Tax	Line - Unit Price	$20.00 / $21.60	Unit price	Optional
Total Ex/Inc Tax	Line - Total	$40.00 / $43.20	Extended price	Optional
Quantity Refunded	Line - Qty Refunded	1	Refunds	Optional
Quantity Shipped	Line - Qty Shipped	1	Fulfillment	Optional
Name	Line - Title	Blue Widget	Item name	Optional
Type	Line - Type	physical/digital	Item type	Optional
UPC/GTIN/MPN	Line - Identifiers	012345678905	Catalog IDs	Optional
Weight	Line - Weight	1.5	Shipping weight	Optional

BigCommerce Field	Maps To	Example	Purpose	Status
Order ID	Order - ID	12345	Unique identifier	Optional
Date Created	Order - Created	2025-04-07T10:00:00Z	Creation date	Required
Status	Order - Status	Awaiting Payment	BC status	Optional
Currency Code/Rate	Order - Currency	USD / 1.0	Currency context	Optional
Subtotal/Tax/Total	Order - Totals	$90/$7.20/$102.60	Financials	Optional
Staff/Customer Notes	Order - Notes	Expedite please	Communication	Optional
Gift Card/Certificate Amount	Order - Gift Amount	$25.00	Payment mix	Optional

• Map BigCommerce “Shipping Method” to your Flxpoint shipping policies (e.g., Standard → Standard, Express → Express).

• Digital items import with type digital.
• Gift certificates without SKU use generated SKUs:
  • With name: name + "-" + orderItemId
  • Duplicate names: type + "-" + orderItemId

• Import FFL Details — enable to read FFL info from Order Comments when present.
• Use rules/flags on FFL-required items for review before fulfillment.

Utility	When it Helps	What it Does
Currency conversion	Normalize totals	Applies rate and rounds per policy.
Quantity guard	Prevent nulls	Ensures missing qty maps to a safe default or fails fast.
State Code preference	Consistent region mapping	Prefer two-letter codes where available.

• Order Acknowledgement — Depends on the Source: if the supplier automatically acknowledges orders, it will be automated; otherwise, configure Source Get Acknowledgement to automate the acknowledgement step.

• Connection shows Connected and Test Connection succeeds.
• Template maps SKU, Quantity, and Date Created.
• State Code mapped for both Billing and Shipping (when present).
• Statuses and Time Frame reflect what you want to import.

• SKU missing — orders/lines without SKU won’t be saved; fix in BC or use allowed generated logic for gift certificates only.
• Quantity null — map Line Quantity (Field). Unmapped quantity can cause errors.
  Cannot invoke "java.lang.Integer.intValue()" because the return value of "BigCommerceProductDto.getQuantity()" is null
  Fix: Templates → Get Orders → Field Mapping → map Quantity → Save → Re-run.
• FFL not imported — enable “Import FFL Details” and confirm details exist in Order Comments.
• Multi-address items missing — ensure Shipping Address fields are mapped at the line-item level if you enabled multiple addresses.
• Rate limits — reduce frequency/batch size; stagger schedules.

Feature	Availability	What to Expect
Statuses filter	Supported	Import across multiple statuses in one run.
Batch size	50/orders page	Processes in pages; total time varies with volume.
Digital/Donations	Supported	Comes as digital item type or generated identifiers.
Gift certificates	Supported	Generated SKU when none exists (see rules above).
PII retention	Configurable	Auto-redact/delete after set window.
Shipping mapping	Supported	Map BC method → Flxpoint policy for routing.

• 1Add Sync Orders: Go to Sales Channels → BigCommerce → Integrations and select Sync Orders. Ensure the BigCommerce connection shows Connected (OAuth/app install).
• 2Configure core settings:
  • Partial Shipments — enable to mark orders as Partially Shipped until all lines ship.
  • Carrier/Provider handling — use valid BigCommerce carriers; if not available, send carrier as empty to avoid errors.
  • Scheduling — optional cadence (e.g., hourly/daily) or run on demand.
• 3Create a Mapping Template: open Templates → Sync Orders, map shipment fields (Tracking Number, Carrier, Method, Costs, Dates, Notes), Save, then Run.

• Flxpoint creates BigCommerce shipments via POST /v2/orders/{order_id}/shipments and updates order status.
• Partially Shipped when only some lines ship; Shipped when complete.
• Customer notification emails are sent by BigCommerce if enabled in store settings.

Template	Use Case	What it Covers	Availability
BigCommerce Sync Orders 1	Post shipments + update status	Tracking Number/URL, Carrier, Method, Costs, Shipped Date, Comments/Notes	Available

Flxpoint Field	BigCommerce Shipment Field	Example	Purpose	Status
Tracking Number	tracking_number	1Z999AA10123456784	Primary tracking identifier	Required
Tracking Link	tracking_url	https://track.ups.com/123456	Direct tracking URL	Optional
Tracking Carrier	carrier	UPS	Carrier used for tracking	Optional
Shipping Provider	carrier (or send empty)	U.P.S.	BC-accepted carrier value	Optional
Shipping Method	shipping_method	Standard Shipping	Service/method label	Optional
Merchant Shipping Cost	shipping_cost	$5.00	Merchant cost	Optional
Date Created	shipped_at	2025-05-26T10:00:00Z	Shipment timestamp	Optional
Comments	comment	Shipped via priority	Notes to include on shipment	Optional

Utility	When it Helps	What it Does
Carrier guard	Unrecognized carriers	Maps invalid carriers to empty so the API accepts the shipment.
Method normalization	Mixed method labels	Standardizes method strings (e.g., “UPS® Ground” → “Ground”).
Tracking URL build	No direct URL provided	Generates a URL from carrier + tracking number.

• Connection shows Connected and passes Test Connection.
• Template maps Tracking Number (required). Tracking URL/Carrier/Method optional but recommended.
• Store’s notification emails are enabled if you expect customer emails.
• Carrier values align to BigCommerce accepted list.

• Invalid carrier — map carrier to empty when your value isn’t recognized by BigCommerce.
• Shipment not created — ensure Tracking Number is mapped via Field and the order_id is correct.
• No customer email — enable shipment notifications in BigCommerce store settings.
• Partial vs full status — verify line-level fulfillment quantities to move from Partially Shipped to Shipped.
• Rate limits — stagger schedules or reduce batch frequency during peak times.

Feature	Availability	What to Expect
API endpoint	Supported	POST /v2/orders/{order_id}/shipments
Partial shipments	Supported	Order status updates to Partially Shipped until complete.
Customer notifications	Store-controlled	Emails dispatched by BigCommerce if enabled.
Carrier handling	Flexible	Use valid value or map to empty.
Scheduling	Optional	Run on demand or via recurring schedule.