This job keeps your Nalpac catalog in sync with Flxpoint:

• Imports products/variants, quantities, brand, categories, and primary images.
• Applies exclusions for discontinued products and zero-cost items.
• Updates your inventory records for downstream channels.

• 1Authenticate — Use your Nalpac API key; ensure any IP allowlisting is configured if required.
• 2Fetch Products — Calls GET /api/productV2?pageNumber=<n>&pageSize=<n>&modifiedAfter=<iso>&excludeDiscontinued=true.
• 3Paginate — Flxpoint iterates pages (recommend ≤100–250 items per page depending on limits).
• 4Apply Exclusions — Skip records where discontinued=true or WholesalePrice == 0.
• 5Map Fields — Source fields are mapped to your template (see table below).
• 6Save Inventory — Data is written to the Global Inventory Pool.

• 1Connect Integration — Select Nalpac as your Source and enter API credentials.
• 2Configure Settings
  • Page Size — 100 is safe; adjust if you encounter rate limits.
  • Archive/Un-Archive Inventory — Enable if this is your only job archiving for this source.
• 3Create Mapping Template — Map SKU, Quantity, Brand, Categories, Price fields, etc.
• 4Save & Schedule — Run manually or schedule (UTC).

Recommended minimum mappings for reliable imports:

• Discontinued Exclusion — The job calls Nalpac with excludeDiscontinued=true to omit discontinued items.
• Zero-Cost Exclusion — Items where WholesalePrice == 0 are not imported.
• Customer Guidance — If valid items appear with WholesalePrice = 0, contact Nalpac to correct cost data. As a fallback, consider Do Not Import rules for specific SKUs.

• Missing products? Confirm they aren’t discontinued and don’t have WholesalePrice = 0.
• Zero quantities? Verify source quantities and mapping to Quantity.
• Auth failures? Re-check API key and any IP allowlisting.
• Rate limits/slow imports? Reduce page size and schedule off-peak hours.
• Audit — Review job logs to confirm exclusions and page-by-page imports.

Schedule this job daily (or more frequently if needed) to keep your catalog up to date. All schedules run in UTC.

• Posts a PO payload to https://api.nalpac.com/api/order.
• Validates order-level details and line items (SKU, quantity, etc.).
• Checks for carrier and method mapping accuracy before finalizing.
• Receives acknowledgements, partial acceptances, or rejections from Nalpac.
• Logs all request/response details to Job History for auditing.

• 1Prepare PO — Build the order JSON from your mapping template (order + lines).
• 2Endpoint Check — Nalpac validates that the PO can be created/processed. If not recognized, an error is returned.
• 3Carrier & Method Matching — Ensure your Carrier Name and Shipping Method map to Nalpac’s values; otherwise you’ll see carrier/method errors.
• 4Post Order — Send POST to /api/order; capture the response including any line-level messages (e.g., “option ID could not be found”).
• 5Auto Acknowledgements — Nalpac often returns PushItem-style confirmations indicating accepted/rejected lines.
• 6Schedule — Run on-demand or on a cadence that fits your order-processing flow.

Each Flxpoint field maps to a Nalpac API field using one of these modes:

• Don’t Map — Ignore the field.
• Set to Empty — Force a blank value.
• Field — Copy from a Flxpoint field (e.g., Fulfillment Request Number → ExternalOrderNumber).
• Value — Provide a fixed value (e.g., “Dropship”).
• Mapping Set — Use a predefined translation list (e.g., internal ship codes → Nalpac codes).
• Rules — Conditional logic (e.g., “If Carrier = FedEx, Method = Ground”).

• PO Recognition — If Nalpac flags the PO as invalid, confirm your ExternalOrderNumber mapping.
• Carrier/Method Mismatch — Validate that Carrier Name and Shipping Method exist in Nalpac’s system (see /carrier).
• SKU Validation — If lines are rejected, confirm SKUs against Nalpac’s catalog.
• Template Accuracy — Re-check critical fields (ExternalOrderNumber, OrderDate, SKU) align with Nalpac’s API.
• Response Logs — Use Job History to identify which fields/lines were rejected and why.

Schedule this job according to your order flow. Many teams run it frequently during business hours. All schedules run in UTC.

• Looks up shipment records by PO Number (or Fulfillment Request #).
• Returns carrier info, tracking number(s), ship dates, and item-level quantities.
• Handles partial shipments by associating items to their corresponding tracking number.
• Writes shipment data back to your order in Flxpoint for downstream notifications.
• Logs the raw response for auditing in Job History.

• 1Identify Order — Use your PO Number or Fulfillment Request Number as poNumber.
• 2Call Endpoint — Request GET https://api2.nalpac.com/api/order?poNumber=<value>.
• 3Parse Response — Read shipment(s): carrier name/method, tracking, ship date, and item associations.
• 4Map & Save — Apply your mapping template to store shipment headers and line-level quantities.
• 5Repeat/ Schedule — Run on a cadence to capture late or partial shipments.

Configure how Nalpac response fields map into your shipment model. Each field can be set to:

• Don’t Map — Ignore the field.
• Set to Empty — Force a blank value.
• Field — Copy directly from the response.
• Value — Use a fixed, custom value.
• Mapping Set — Translate using a predefined lookup (e.g., carrier code mappings).
• Rules — Conditional logic based on data (e.g., map USPS-like methods to “USPS Ground”).

• No shipments found? Verify the exact poNumber / FR # passed to the endpoint.
• Carrier/method missing? Normalize response values to your internal carrier/method mapping sets.
• Partial shipments not linking? Ensure line-item association is saved per tracking number, not per order.
• Parsing issues? Inspect the Job History raw response to confirm field names and nesting.
• Time zone/format problems? Confirm your parser handles ISO timestamps for Shipped At.

Schedule this job to run periodically (e.g., hourly or several times daily) to pick up new or late shipment events. All schedules run in UTC.