Parts Unlimited as a Source
Summary
PartsNetWeb connects automotive parts distributors that publish through PartsNetWeb portals. Inventory imports over FTP/SFTP via Get Inventory (Primary), while Send Fulfillment Requests and Get Shipments run over the PartsNetWeb API using a separate Dealer Number and API Token. All three operations (inventory, fulfillment, and shipment tracking) are supported.
PartsNetWeb uses two separate connections: an FTP/SFTP connection for Get Inventory Primary, and a PartsNetWeb API connection for Send Fulfillment Requests and Get Shipments. Add a PartsNetWeb source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.
| Field | What to enter |
|---|---|
Dealer IDRequired | Your PartsNetWeb Dealer ID. |
FTP HostRequired | The FTP/SFTP server for your PartsNetWeb inventory feed. |
FTP PortRequired | The connection port. |
FTP UserRequired | Your FTP/SFTP username. |
FTP PasswordRequired | Your FTP/SFTP password. |
Remote PathRequired | The directory on the FTP/SFTP server where the inventory feed file resides. |
| Field | What to enter |
|---|---|
API TokenRequired | Your PartsNetWeb API access token. |
API Base URLRequired | The PartsNetWeb API endpoint provided for your account. |
Dealer NumberRequired | Your PartsNetWeb Dealer Number, used for order and shipment operations. |
Inventory is FTP-based, orders are API-based
Get Inventory Primary uses the FTP/SFTP connection (Dealer ID plus FTP host, port, user, and password), while Send Fulfillment Requests and Get Shipments use the API Token, API Base URL, and Dealer Number. These are separate credential sets.
Set the Remote Path to the inventory file
Get Inventory needs the Remote Path pointing to the directory where the inventory feed resides, or the file will not be found.
Archive/Un-archive keeps inventory accurate
Enable archiving so items missing from the feed are archived, and automatically un-archived when they reappear, keeping stock aligned with the source.
Use Post-Mapping Workflows to exclude brands
A Post-Mapping rule (for example, Brand in list → Do Not Import) prevents importing inventory for brands you do not carry.
Imports the PartsNetWeb catalog: products, attributes, images, and quantity.
| Field | Maps To: Notes |
|---|---|
| Attribute (abbreviation) | → Product → Attributes. Looked up from PartsNetWeb's abbreviation to its full attribute name. |
| Images | → Product / Variant → Images. Imported and marked fetched. |
| Quantity | → Inventory Variant → Quantity. Available units from the feed. |
| Category | → Product → Category One / Two. PartsNetWeb does not provide vendor categories: both are set to General. |
| Remaining catalog fields (SKU, price, etc.) | → Product / Variant. Mapped per your field-mapping template from the PartsNetWeb product feed. |
Sends fulfillment requests to PartsNetWeb for dropship order fulfillment.
| Field | Maps To: Notes |
|---|---|
| Fulfillment Request → Line Items | → Order Line Items. Required. Request is rejected if no line items are mapped. |
| Source Shipping Method | → Ship Method. Looked up against PartsNetWeb's supported shipping options; a warning logs if unmapped. |
| PartsNetWeb response → Reference Number | No mapping/field is available. |
Pulls PartsNetWeb shipment confirmations: ship date, cost, and items.
| Field | Maps To: Notes |
|---|---|
| ShipDate | → Shipment → Shipped At. Falls back to the current time if PartsNetWeb doesn't return a ship date. |
| DropShipFee | → Shipment → Shipping Cost. PartsNetWeb's dropship fee for the shipment. |
| ItemList | → Shipment → Items. Each shipped line item, matched back to the originating order. |
| Purchase Order / Order references | → Shipment → Purchase Order ID, Order ID. Associates the shipment to the originating Flxpoint order and PO. |