Accutech as a Source

July 17, 2026

Summary

Accutech Electronics is a pre-built electronics integration in Flxpoint. It supports two connection types — FTP (Basic Auth) using FTP Protocol, Host, Port, User and Password, or Accutech API (direct) using Environment, Partner ID, Password and User ID. The integration runs Get Inventory (Primary daily, Secondary for frequent pricing/quantity refreshes), Send Fulfillment Requests, and Get Shipments. Use the connection type your Accutech representative specifies; for operation-level mapping guidance contact support@flxpoint.com.

What this integration does

Get Inventory (Primary)

Imports Accutech's full electronics catalog — run once daily. Brings in products, pricing and quantity for the complete catalog.

Get Inventory (Secondary)

A lighter, more frequent refresh of pricing and quantity only, to keep cost and stock current between daily full runs.

Send Fulfillment Requests

Sends orders (Fulfillment Requests) to Accutech for dropship fulfillment.

Get Shipments

Pulls Accutech shipment confirmations — ship date and tracking — back into Flxpoint.

How to connect - credentials you need

Accutech supports two connection types. Use the one your Accutech representative specifies for your account. Add an Accutech source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

Option A — FTP (Basic Auth)

FTP ProtocolRequired

The FTP protocol to use (FTP or FTPS), as provided by Accutech.

HostRequired

The Accutech FTP server hostname.

PortRequired

The FTP port for the connection.

UserRequired

Your Accutech FTP username.

PasswordRequired

Your Accutech FTP password.

Option B — Accutech API

EnvironmentRequired

Toggles Test (Sandbox) vs Production. Use Test during setup, then switch to Production before go-live.

Partner IDRequired

Your Accutech Partner ID, provided by Accutech (separate from any website login).

User IDRequired

Your Accutech API User ID.

PasswordRequired

Your Accutech API password.

Both connection types include Advanced Settings: Maintain Constant Connection (optional) and Use Unbuffered Private Data Channel — enable the latter only if FTPS Test Connection fails with a 534 SSL policy error. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.

Important - read before configuring

Two connection types — FTP (Basic Auth) or Accutech API (Partner ID + User ID + Password)

The Accutech connection supports two methods: FTP (Basic Auth) — requires FTP Protocol, Host, Port, User, and Password; and Accutech (direct API) — requires Environment, Partner ID, Password, and User ID. Both types include Advanced Settings: Maintain Constant Connection (optional) and Use Unbuffered Private Data Channel (for FTPS 534 SSL policy errors only). Use the connection type your Accutech representative specifies for your account.

FTPS 534 errors — enable Use Unbuffered Private Data Channel in Advanced Settings

If FTP Test Connection fails with a 534 SSL policy error when using FTPS, open Advanced Settings on the connection and enable Use Unbuffered Private Data Channel. This setting is available on both FTP and Accutech API connection types and resolves SSL policy conflicts specific to FTPS. Do not enable it for standard FTP connections — only for FTPS.

GIP daily for full catalog; GIS more frequently for delta updates — Archive on one job only

Run Get Inventory Primary once daily to import Accutech's full electronics catalog. Use Get Inventory Secondary more frequently for pricing and quantity refreshes. Enable Archive/Un-Archive on one job only — enabling it on both GIP and GIS simultaneously causes products to toggle between archived and active states unexpectedly.

For operation-specific setup and mapping guidance, contact Flxpoint Support

Extended configuration documentation for Accutech — including required Send FR fields, Get Shipments mapping, and any Accutech-specific API behavior — is available from Flxpoint Support. Email support@flxpoint.com with your account details and the operations you need to configure.

Operations - fields to know

Get Inventory (Primary) Get Inventory (Secondary) Send Fulfillment Requests Get Shipments

Accutech Field	Maps To — Notes
accutechSKU	→ Product / Variant → SKU. Required. Primary identifier for the catalog item.
price	→ Pricing → Cost. Your Accutech dealer price, saved as Cost.
totalQuantity	→ Inventory → Quantity. Total available units across locations.
locations	→ Inventory → Per-warehouse quantity. Accutech returns stock per location (e.g. CA / PA warehouses).
mfgCode	→ Identifiers → Manufacturer Code / MPN. Manufacturer part reference.

Accutech Field	Maps To — Notes
sku	→ Inventory Variant → SKU. Required. Primary identifier.
price	→ Pricing → Cost. Dealer price saved as Cost.
quantity	→ Inventory → Quantity. Current available units.
Full catalog fields	Not included in Secondary — titles, categories and identifiers come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost and Quantity current.

Source Field	Maps To (Accutech) — Notes
Fulfillment Request line → SKU	→ Order Item SKU. Required. Sent to Accutech per line item.
Fulfillment Request line → Quantity	→ Order Item Quantity. Required. Units requested.
Shipping address	→ Ship To. Required. End-customer shipping address.
Ship-to contact	→ Ship To Contact. Contact name/details for the shipment.
Source Shipping Method	→ Ship Method. The shipping method sent to Accutech for the order.

Accutech Field	Maps To — Notes
ShipDate	→ Shipment → Shipped At. When Accutech marks the shipment shipped.
TrackNumber	→ Shipment → Tracking Number. Required. Package tracking number.
ShipMethod	→ Shipment → Ship Method. Carrier/method description returned by Accutech.
Item SKU	→ Shipment Item → SKU. Required. Associates the shipped line to your catalog.
ShipQuantity	→ Shipment Item → Quantity. Required. Units shipped for the line.
PONumber / InvoiceNumber	→ Shipment references. Accutech PO and invoice numbers for reconciliation.

Common issues

FTP Test Connection failing — 534 SSL policy error

A 534 error on FTPS connections means the FTP server enforces SSL/TLS but there is a protocol conflict. Go to the FTP connection → Advanced Settings and enable Use Unbuffered Private Data Channel. Save and re-test. If using standard FTP (not FTPS) and seeing a 534 error, confirm the correct FTP protocol is selected — standard FTP does not use SSL. For all other FTP authentication failures, verify Host, Port, Username, and Password exactly as provided by Accutech.

Accutech API Test Connection failing — invalid Partner ID, User ID, or Password

If the Accutech API connection fails: (1) re-enter Partner ID, User ID, and Password exactly as provided by Accutech — these are separate from any Accutech website login; (2) confirm the correct Environment is selected (Test vs Production) — credentials often differ between environments; (3) if credentials are correct but the test still fails, contact your Accutech representative to confirm API access is enabled for your account and that the credentials have not expired or been rotated.

FAQs

Which connection type should I use — FTP or Accutech API?▸

Both connect to Accutech's data but via different methods. FTP (Basic Auth) uses standard FTP file retrieval (host, port, user, password) — suitable if Accutech has provisioned an FTP feed for your account. Accutech API uses direct API authentication (Environment, Partner ID, Password, User ID) — suitable if Accutech has provisioned API access. Confirm with your Accutech account representative which method your account is configured for. If unsure, try the Accutech API type first — it typically provides more direct access to pricing and inventory data.

What is the Environment field on the Accutech API connection?▸

The Environment field toggles between Test (Sandbox) and Production modes for the Accutech API. Use Test during initial setup to verify credentials and mapping without affecting live orders or inventory. Switch to Production once your configuration is validated. Leaving the connection in Test mode after go-live will cause order operations (Send FR, Get Shipments) to use the test environment — orders may succeed in Flxpoint but will not process through Accutech's live system.

Back to Electronics