Nalpac is a premier distributor of adult products and novelties, delivering quality merchandise and timely shipments. Integrated with Flxpoint, Nalpac streamlines inventory updates and order processing for effortless management. This guide offers a comprehensive overview to help you efficiently retrieve and map shipment data from Nalpac's API.
How to Connect
Step 1: Log into your Flxpoint account and navigate to the Sources tab.
Step 2: Click on Configure Single Source (or + Add Source)
to begin creating a new source.
Step 3: Fill in your source details (e.g., vendor name, fulfillment preferences).
Once completed, click Save.
Step 4: After saving, navigate to
Get Inventory under Integrations in the left menu. If you see
"No integrations have been configured for this process yet",
click Start Creating Integrations.
Step 5: From the list of Custom Integrations or Standard Integrations,
locate and select Nalpac. This will open the connection setup screen.
Step 6: In the New Nalpac Connection form (or “Edit Nalpac Connection” if you are updating),
enter your Connection Name, Username, and Password.
If there are additional fields or advanced options (e.g., specific endpoints, token-based authentication), complete them as instructed by Nalpac.
If there are additional fields or advanced options (e.g., specific endpoints, token-based authentication), complete them as instructed by Nalpac.
Step 7: Click Test Connection to ensure your credentials
are valid. Once verified, click Save Connection.
Step 8: On the Configure Settings screen, you can
enable or disable the Archive/Un-Archive Inventory option.
- If enabled: Any item missing from Nalpac’s feed will be marked as “archived” in Flxpoint. - If later found: Items are automatically “un-archived” and updated.
Adjust any other settings as needed, then click Save and Proceed.
- If enabled: Any item missing from Nalpac’s feed will be marked as “archived” in Flxpoint. - If later found: Items are automatically “un-archived” and updated.
Adjust any other settings as needed, then click Save and Proceed.
Step 9: Under Define a Mapping Template, select or create a
Nalpac Mapping Template. Map fields from Nalpac’s inventory feed
(e.g., SKU, Quantity, Price) to Flxpoint’s corresponding fields. Once mapped,
click Save and Complete.
Step 10: Your Nalpac “Get Inventory” integration is now active.
Flxpoint will begin retrieving inventory data from Nalpac according to your configured schedule.
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates.
Get Inventory (Primary)
Supported: Nalpac - Get Inventory [Primary]
This integration supports the retrieval of product data from your Nalpac account. It fetches product details from
Once fetched, Flxpoint will create or update inventory records based on your configured mapping rules.
This integration supports the retrieval of product data from your Nalpac account. It fetches product details from
https://api.nalpac.com/api/product in batches
of up to 100 items per page. Flxpoint automatically paginates through the feed to retrieve
your entire inventory.
- Frequency: Schedule this job daily or weekly to keep data current.
- Data Format: JSON feed that includes fields such as SKU, Quantity On Hand, Manufacturer, MSRP, etc.
- Authentication: Ensure your API credentials are valid and that your IP or server is whitelisted if required by Nalpac.
Once fetched, Flxpoint will create or update inventory records based on your configured mapping rules.
Mapping Template Overview
For the Get Inventory Primary operation, you need to define how Nalpac’s inventory fields map to your internal fields. All the information provided in the mapping template code is relevant. You have several mapping options for each field:
1. Product Identification
2. Inventory Details
3. Product Attributes
Additional Notes:
For the Get Inventory Primary operation, you need to define how Nalpac’s inventory fields map to your internal fields. All the information provided in the mapping template code is relevant. You have several mapping options for each field:
- Don’t Map: Exclude this field from processing.
- Set to Empty: Force this field to remain blank.
- Field: Directly copy the value from a source field (e.g., copy Nalpac SKU to your internal SKU).
- Value: Use a fixed or static value for every record.
- Mapping Set: Apply a predefined transformation or lookup table to convert source values.
- Rules: Use conditional logic to set the field value based on specific criteria.
1. Product Identification
Nalpac SKU → Internal SKU
This unique identifier must match exactly with your internal records.
This unique identifier must match exactly with your internal records.
Product Name → Internal Product Title
Ensures consistency in how products are identified in your catalog.
Ensures consistency in how products are identified in your catalog.
Barcode/UPC → Internal Barcode
Useful for cross-referencing products across different systems.
Useful for cross-referencing products across different systems.
2. Inventory Details
Quantity On Hand → Available Quantity
Reflects the current stock level. Accurate mapping is essential to prevent overselling.
Reflects the current stock level. Accurate mapping is essential to prevent overselling.
Cost Price → Internal Cost
If required, map this field to monitor purchase costs.
If required, map this field to monitor purchase costs.
Wholesale Price → Internal Wholesale Price
Optional; used for pricing strategies and margin calculations.
Optional; used for pricing strategies and margin calculations.
3. Product Attributes
Manufacturer → Brand Name
Helps with categorizing products by brand.
Helps with categorizing products by brand.
Category → Internal Category
Aligns Nalpac’s product categories with your own classification.
Aligns Nalpac’s product categories with your own classification.
Additional Notes:
- Verify that all mapped fields conform to both your system’s format and Nalpac’s requirements.
- Use fixed values, mapping sets, or rules where necessary to standardize data.
- Review Flxpoint’s logs after each inventory import to ensure that the mappings are applied correctly and that no critical data is omitted.
Troubleshooting Tips
If the inventory feed fails or data is not imported correctly, consider the following:
For further assistance, contact Flxpoint support with any error messages or logs from your job history.
If the inventory feed fails or data is not imported correctly, consider the following:
- Check Credentials: Confirm that your API key and IP whitelisting settings are correct.
- Pagination Issues: Ensure that Flxpoint is iterating through all pages (up to 100 products per page).
- Field Mapping: Verify that essential fields like SKU and Quantity are properly mapped.
- Schedule Conflicts: Avoid overlapping jobs which can cause partial updates.
For further assistance, contact Flxpoint support with any error messages or logs from your job history.
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.
Send Fulfillment Requests
Nalpac - Send Fulfillment Requests [Primary]
This operation submits purchase orders (fulfillment requests) to Nalpac via
Once the request is accepted, Nalpac processes the order for shipment. You can then use Flxpoint to monitor shipping updates, confirmations, or any subsequent rejections in your Job History and Logs.
This operation submits purchase orders (fulfillment requests) to Nalpac via
https://api.nalpac.com/api/order. Once sent, Nalpac will either acknowledge the order, reject it, or respond with partial acceptance if any lines are invalid.
- Endpoint Check: We first confirm the PO exists on
Nalpac’s side. If it doesn’t, Nalpac returns an error indicating the
PO is not recognized.
- Carrier & Method Matching: Nalpac checks the
“Carrier Name” and “Shipping Method.” If no match is found, you may
see errors like “Carrier name could not be found” or
“Shipping method not found.”
- Line-Item Validation: If any requested SKUs are
unrecognized, you may receive a partial acceptance or line-item
failure notice (e.g., “option ID could not be found”).
- Auto Acknowledgements: Nalpac often sends back
“PushItem” confirmations indicating the lines accepted or rejected.
- Schedules & Frequency: You can schedule these
fulfillment requests in Flxpoint at any interval that suits your
order-processing flow.
Once the request is accepted, Nalpac processes the order for shipment. You can then use Flxpoint to monitor shipping updates, confirmations, or any subsequent rejections in your Job History and Logs.
Mapping Template Overview
When sending a Purchase Order (Fulfillment Request) to Nalpac, you’ll configure how each Flxpoint field maps to Nalpac’s API fields. You can set each mapping to:
Below is a summary of the key fields to consider. Your actual template might have more (or fewer) fields, but this list shows the most common mappings:
1. Order-Level Fields
2. Shipping & Carrier Fields
3. Shipping Address Fields
4. Line-Item Fields
Tip: If Nalpac rejects or partially accepts an order, double-check these mappings, especially Carrier, Shipping Method, SKU, and ExternalOrderNumber—to ensure they line up with Nalpac’s recognized fields.
Adjust or refine these mappings as needed so Flxpoint’s fields properly match Nalpac’s Purchase Order structure.
When sending a Purchase Order (Fulfillment Request) to Nalpac, you’ll configure how each Flxpoint field maps to Nalpac’s API fields. You can set each mapping to:
- Don’t Map: Ignore the field entirely.
- Set to Empty: Force Nalpac’s field to be blank.
- Field: Copy directly from a Flxpoint field (e.g.,
Fulfillment Request Number → Nalpac ExternalOrderNumber).
- Value: Use a fixed value for all orders or items
(e.g., “Dropship”).
- Mapping Set: Apply a predefined list/transformation
(e.g., your internal shipping codes → Nalpac’s recognized codes).
- Rules: Use conditional logic
(e.g., “If Carrier = ‘FedEx’, then set Method = ‘Ground’”).
Below is a summary of the key fields to consider. Your actual template might have more (or fewer) fields, but this list shows the most common mappings:
1. Order-Level Fields
Fulfillment Request Number →
Nalpac ExternalOrderNumber
This uniquely identifies the PO at Nalpac. If not recognized, Nalpac may reject the order.
This uniquely identifies the PO at Nalpac. If not recognized, Nalpac may reject the order.
Order Date →
Nalpac OrderDate
Optional but recommended so Nalpac knows when the order was placed.
Optional but recommended so Nalpac knows when the order was placed.
PO Number →
Nalpac PoNumber
If you use a separate internal PO #, you can map it here (optional).
If you use a separate internal PO #, you can map it here (optional).
Packing Slip Type / Delivery Instructions →
Nalpac Delivery Instructions
Only if Nalpac supports special instructions. Otherwise, set to Don’t Map or Set to Empty.
Only if Nalpac supports special instructions. Otherwise, set to Don’t Map or Set to Empty.
Order Notes →
Nalpac Note
General text field for additional info. Often optional.
General text field for additional info. Often optional.
Signature Required →
Nalpac SignatureRequired
If Nalpac offers signature services, you can set a boolean or specific value. Otherwise, Don’t Map.
If Nalpac offers signature services, you can set a boolean or specific value. Otherwise, Don’t Map.
2. Shipping & Carrier Fields
Carrier Name →
Nalpac “Name” Field
From Jira notes: the carrier’s name in Flxpoint must map to Nalpac’s
From Jira notes: the carrier’s name in Flxpoint must map to Nalpac’s
Name field to avoid mismatch errors.
Description →
Nalpac “Default Method Code”
Also from Jira: shipping method descriptions should go into
Also from Jira: shipping method descriptions should go into
Default Method Code in Nalpac’s system.
Shipping Method →
Nalpac Method / Shipping Code
Must match exactly what Nalpac has in
Must match exactly what Nalpac has in
/carrier.
If it doesn’t, you’ll see “Shipping method not found.”
Ship To Email Address →
Nalpac Email
Used if Nalpac requires an email for shipping notifications.
Used if Nalpac requires an email for shipping notifications.
Ship To Phone Number →
Nalpac Phone
Set if Nalpac needs a phone contact for deliveries.
Set if Nalpac needs a phone contact for deliveries.
3. Shipping Address Fields
Address1 / Address2 / Address3 →
Nalpac Address Line 1 / 2 / etc.
Flxpoint might have multiple lines; map them accordingly. If Nalpac only uses two lines, set the extra to Don’t Map.
Flxpoint might have multiple lines; map them accordingly. If Nalpac only uses two lines, set the extra to Don’t Map.
City →
Nalpac City
State →
Nalpac State
Use the full name or 2-letter code, depending on Nalpac’s format.
Use the full name or 2-letter code, depending on Nalpac’s format.
Zip Code →
Nalpac PostalCode
Country →
Nalpac Country
Name →
Nalpac FullName
If your shipping address includes a “Name” field, map it here. Otherwise, you can Don’t Map.
If your shipping address includes a “Name” field, map it here. Otherwise, you can Don’t Map.
4. Line-Item Fields
SKU →
Nalpac SKU
Identifies each product line. A mismatch leads to partial acceptance or error (“option not found”).
Identifies each product line. A mismatch leads to partial acceptance or error (“option not found”).
Quantity →
Nalpac Quantity
How many units to order for that SKU.
How many units to order for that SKU.
Cost →
Nalpac Cost
If needed. If Nalpac doesn’t require cost in the PO, set to Don’t Map.
If needed. If Nalpac doesn’t require cost in the PO, set to Don’t Map.
Title / UPC / MPN →
Nalpac Title / UPC / MPN
Optional, but can help Nalpac cross-reference items if they support it.
Optional, but can help Nalpac cross-reference items if they support it.
PO Line Item # →
Nalpac PO Line Item
If you track line numbers or references, you can map them. Otherwise, Don’t Map.
If you track line numbers or references, you can map them. Otherwise, Don’t Map.
Tip: If Nalpac rejects or partially accepts an order, double-check these mappings, especially Carrier, Shipping Method, SKU, and ExternalOrderNumber—to ensure they line up with Nalpac’s recognized fields.
Adjust or refine these mappings as needed so Flxpoint’s fields properly match Nalpac’s Purchase Order structure.
Troubleshooting Tips
If your Send Fulfillment Requests job fails or Nalpac partially accepts your order, keep these points in mind:
For further assistance, contact Flxpoint support with any error messages or logs you have from your job history. Nalpac’s support can also clarify any carrier/method or SKU mismatches if needed.
If your Send Fulfillment Requests job fails or Nalpac partially accepts your order, keep these points in mind:
- PO Recognition: If Nalpac returns an error that the
PO is invalid, ensure your Fulfillment Request Number is mapped
correctly.
- Carrier/Shipping Method Mismatch: Verify the
“Carrier Name” and “Shipping Method” you’re sending exist in Nalpac’s
system. Use
/carrier to find valid methods.
- SKU Validation: If Nalpac rejects certain SKUs,
confirm those SKUs match Nalpac’s product catalog. A mismatch leads
to partial acceptance or line failures.
- Mapping Template Accuracy: Double-check your
field mappings, especially ExternalOrderNumber, Order
Date, and SKU fields, to ensure they align with
Nalpac’s API requirements.
- Response Logs: Flxpoint logs each request and
Nalpac’s response. Use these logs to identify which line items or
fields Nalpac may be rejecting.
For further assistance, contact Flxpoint support with any error messages or logs you have from your job history. Nalpac’s support can also clarify any carrier/method or SKU mismatches if needed.
Get Shipments
Nalpac - Get Shipments [Primary]
This operation retrieves shipment tracking information from Nalpac’s API. We call
This operation retrieves shipment tracking information from Nalpac’s API. We call
https://api2.nalpac.com/api/order?poNumber=xxx-xxxx, passing the
Fulfillment Request number (or PO number) as a parameter. Nalpac returns details
about each shipment, including carrier, tracking number, and line items shipped.
- Operation Workflow: Fetch tracking details using the endpoint. The “PO Number” or “FR #” is passed as a query parameter, and Nalpac returns shipment data (carrier info, tracking numbers, and SKUs/quantities). Multiple shipments may be returned for partial orders.
- Key Operation Data: Carrier & Methods, Shipment Item Association, Partial Shipments (if only some SKUs ship), and note that Invoice Information and Custom Fields are not supported.
Mapping Template Overview for Get Shipments
When retrieving shipment tracking details from Nalpac, you need to configure how each field from Nalpac’s response maps to your system’s shipment data. You can set each mapping option as follows:
Below is a summary of the key fields to configure:
1. Shipment-Level Fields
2. Shipment Item-Level Fields
Tip: Double-check these mappings—especially Carrier, Tracking Number, SKU, and Ship Date—to ensure they match Nalpac’s API response and avoid data mismatches.
When retrieving shipment tracking details from Nalpac, you need to configure how each field from Nalpac’s response maps to your system’s shipment data. You can set each mapping option as follows:
- Don’t Map: Ignore this field entirely.
- Set to Empty: Force the field to be blank.
- Field: Copy data directly from a Nalpac field.
- Value: Use a fixed, custom value.
- Mapping Set: Apply a predefined transformation.
- Rules: Use conditional logic to determine the mapping.
Below is a summary of the key fields to configure:
1. Shipment-Level Fields
Carrier: Map the shipment’s carrier information to your system’s Carrier field. This is critical for identifying the shipping partner.
Note: Map any additional shipment information or special instructions provided in the response.
Ship Date (Shipped At): Map the date and time when the shipment was processed, which helps track when the shipment left the facility.
Tracking Number: Map the tracking number returned by Nalpac to monitor shipment progress and delivery status.
2. Shipment Item-Level Fields
Quantity: Map the number of items shipped for each SKU.
SKU: Map the Stock Keeping Unit to identify the specific product. This is essential for inventory reconciliation and order fulfillment.
Tip: Double-check these mappings—especially Carrier, Tracking Number, SKU, and Ship Date—to ensure they match Nalpac’s API response and avoid data mismatches.