Flxpoint Help Center
All DocsContact support

Nalpac as a Source

July 17, 2026

Summary

Nalpac is a pre-built adult products and novelties distributor integration in Flxpoint. The connection uses a single connection type — Nalpac API authenticated with a Username and Password. The integration runs Get Inventory (Primary), Send Fulfillment Requests, and Get Shipments. For operation-level mapping guidance contact support@flxpoint.com.

Get Inventory (Primary)
Imports the full Nalpac catalog daily — products, pricing, and quantity.
Send Fulfillment Requests
Sends orders (Fulfillment Requests) to Nalpac.
Get Shipments
Pulls Nalpac tracking numbers and ship dates back into Flxpoint.

Nalpac supports one connection type — direct API authentication with your Nalpac account Username and Password. Add a Nalpac source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test ConnectionSave Connection.

UsernameRequired
Your Nalpac API username, provided by your Nalpac account representative.
PasswordRequired
Your Nalpac API password.
Test Connection validates your Username and Password before the connection is saved. Send Fulfillment Requests requires the Carrier Name and Shipping Method values to match Nalpac's exactly — confirm the accepted values with your Nalpac representative.

GIP excludes discontinued items and zero-cost SKUs automatically

GIP calls Nalpac's API with excludeDiscontinued=true — discontinued products are never imported. Additionally, any item where WholesalePrice == 0 is excluded. If valid SKUs appear missing after GIP, check first whether the product is marked discontinued or has a zero WholesalePrice in Nalpac's system. Contact Nalpac to correct cost data if legitimate products are being excluded.

Send FR carrier and shipping method must match Nalpac's configuration exactly

The most common order rejection cause is a carrier name or shipping method mismatch — Nalpac returns errors like "Carrier name could not be found" or "Shipping method not found." Map your Carrier Name and Shipping Method to Nalpac's exact accepted values (confirm them with your Nalpac representative). Use a Mapping Set to translate internal codes to Nalpac's values.

Send FR supports partial acceptance — some lines may be rejected while others proceed

Nalpac may return a partial acceptance response for a single order: valid line items proceed while invalid lines (unrecognized SKU, zero quantity, etc.) are rejected. The job logs all request/response details to Job History. After submitting an order, review the job log to identify any rejected lines and their specific error messages before resubmitting.

Get Shipments: lookback by PO number, supports multiple tracking per order (comma-separated)

Get Shipments looks up shipments by the PO/FR Number. Multiple shipments may be returned for the same order (partial shipments). If Nalpac returns multiple tracking numbers, they are stored and displayed together. Schedule Get Shipments hourly or several times daily to capture new and partial shipment events. Archive on GIP only.


FieldMaps To — Notes
SkuProduct / Variant → SKU. Required. Primary identifier for the catalog item.
NameProduct → Title.
DescriptionProduct → Description. Returned pre-stripped of HTML (Flxpoint requests stripDescriptionHTML=true).
WholesalePricePricing → Cost. Your Nalpac dealer price, saved as Cost.
Msrp / MinimumAdvertisedPricePricing → MSRP / MAP.
QuantityOnHand / AvailableQuantityInventory → Quantity. Available units.
Weight / Height / Length / WidthShipping → Dimensions & Weight.
Manufacturer / ManufacturerNumber / UpcIdentifiers → Brand / MPN / UPC.
CategoriesProduct → Category / Subcategory. Nalpac's Parent > Child category string is split into two levels.
AttributesProduct → Attributes. Each Nalpac attribute name/value pair is copied as a product attribute.
Image (matched by SKU from Nalpac's image feed)Product / Variant → Images.
Discontinued / SellableVariant → Custom Fields (discontinued, sellable, stored as Y/N). Note: Flxpoint also requests Sellable=true and excludeDiscontinued=true server-side, so discontinued/non-sellable items are normally filtered out before they reach Flxpoint at all.
Source FieldMaps To (Nalpac) — Notes
Fulfillment Request NumberExternalOrderNumber. Required. Also used to check for an existing order before sending, to prevent duplicates.
PO NumberPoNumber. Used together with the FR date to validate against an existing Nalpac order.
Order DateOrderDate. Sent as yyyy-MM-dd'T'HH:mm:ss.SSSXXX; falls back to the current date/time if the source date can't be formatted.
Carrier Name→ resolved against Nalpac's carrier list to determine the Nalpac Shipping Option. Required — must match a Nalpac carrier name (case-insensitive) or the order fails before it's sent.
Shipping Method→ resolved against the matched carrier's ShippingOptions[].Description to determine the Nalpac Shipping Option ID. Required — must match exactly (case-insensitive).
Shipping address (Name, Address1–3, City, State, Zip, Country)ShippingAddress. Required.
Ship-to phone / emailShipToPhoneNumber / ShipToEmailAddress. Optional.
Delivery instructionsDeliveryInstructions. Optional.
Fulfillment Request line → SKU / Quantity / Unit of MeasureCreateOrderRequestLines[].Sku / Quantity / UnitOfMeasure. Sku and Quantity required per line.
FieldMaps To — Notes
Package → TrackingNumberShipment → Tracking Number. Required — only packages with a tracking number are imported.
Package → ShipDateShipment → Shipped At.
Order-level CarrierShipment → Carrier.
Order-level OrderNumber / PoNumber→ cross-referenced back to the originating Purchase Order / Fulfillment Request in Flxpoint.
Package → Items[].SkuShipment Item → SKU. Required.
Package → Items[].QuantityShipment Item → Quantity. Required.
OrderNotes (if present)Shipment → Note.

Missing products after GIP — SKUs not importing
Two automatic exclusions remove products from GIP: (1) discontinued = true — the item has been marked discontinued in Nalpac's system; (2) WholesalePrice == 0 — zero-cost items are excluded to prevent unusable records. To diagnose: check Job History for exclusion log entries; verify the SKU in Nalpac's portal to confirm its status and cost. If a valid product has WholesalePrice = 0, contact Nalpac to correct the cost data. As a workaround for specific excluded SKUs, consider a "Do Not Import" rule targeting those SKUs.
Send FR rejected — "Carrier name could not be found" or "Shipping method not found"
This is the most common Send FR failure for Nalpac. Nalpac requires that Carrier Name and Shipping Method match values it recognizes exactly. To fix: (1) review Nalpac's accepted carrier and method values (confirm them with your Nalpac representative); (2) in your Send FR mapping template, update the Carrier Name and Shipping Method mappings to use Nalpac's exact values; (3) if your internal carrier/method codes differ, create a Mapping Set that translates your codes to Nalpac's values; (4) re-run the affected orders after correcting the mapping.

What does GIP import from Nalpac and what fields are available?
GIP retrieves the product catalog with pagination. Core mappings: SKU → SKU (required), Name → Title, Quantity On Hand → Quantity, Manufacturer → Brand, Category Level 1–3 → Categories, Image → Image URL, Weight/Width/Height/Depth → Shipping dimensions, Wholesale Price → Cost, MSRP/Price → MSRP/Price. GIP auto-excludes discontinued items. Run daily. Enable Archive/Un-Archive on GIP (not on both GIP and GIS).
What are the required fields for Send FR to Nalpac?
Required order-level: Fulfillment Request Number → External Order Number. Optional but recommended: Order Date, PO Number. Required shipping: Carrier Name (must match Nalpac exactly), Shipping Method (exact match to Nalpac's accepted values). Required address: Address 1/2/3, City, State, Postal Code, Country, Full Name. Required line items: SKU, Quantity. Optional: Cost, Title, UPC, MPN. Use a Mapping Set to translate internal carrier/method codes to Nalpac's values.
How does Get Shipments handle partial shipments?
Get Shipments looks up shipments by the PO/FR Number. Multiple shipments may return for one PO — Flxpoint handles each shipment record separately, associating items to their tracking number. Shipment-level fields: Carrier name/code → Carrier, Method/Service → Shipping Method, Tracking Number → Tracking Number, Ship Date → Shipped At. Item-level: SKU, Quantity. If carrier/method values aren't mapping correctly, use Mapping Sets to normalize Nalpac's response values to your internal carrier/method codes.
© 2026 Flxpoint. All rights reserved.