• POST Sales Orders to record/v1/salesorder (NetSuite REST).
• Support internal warehouse (SO only) vs external/dropship (SO + PO).
• Map customer/header/line fields, including custom fields.

• 1 Create SO: We create a Sales Order when the order is eligible.
• 2 Routing: Internal FR → SO only. External (dropship) FR → SO + PO.
• 3 SKU handling: Choose to send PO-level SKU or Order-level SKU (exploded SKUs supported).
• 4 Customer logic: If Customer Id is mapped, use it; else find by Email, then by Name; if not found, Flxpoint creates the customer and uses that Id.

Partial invoicing is supported. When a vendor bills only some PO lines:

• First bill: Send all lines; for not-yet-billed items use quantity: 0.
• Later bill(s): Send only newly invoiced items with billed quantities.

{
  "items": [
    { "orderLine": 1, "quantity": 1 },
    { "orderLine": 2, "quantity": 0 }
  ]
}

{
  "items": [
    { "orderLine": 2, "quantity": 1 }
  ]
}

• 1 Enable the operation: Accounting → Send Accounting Orders.
• 2 Connection: Use your NetSuite connection (Production or Sandbox). Test → Save.
• 3 Template: Select/create mapping and choose SKU option (PO-level vs Order-level).
• 4 Schedule: Turn on Scheduled and set a cadence (e.g., Every 30 Minutes).

• Customer not created/found → provide Customer Id or ensure Email/Name mapping exists.
• Wrong SKUs on lines → verify template choice (Order-level vs PO-level) and vendor associations.
• SO created but no PO → check FR type (PO generation only for external/dropship).
• Validation errors → confirm IDs (Category, Custom Form, Entity Status, Subsidiary) match NetSuite values.

• Create Item Fulfillments when shipments occur.
• Attach one or many tracking numbers.
• Fulfill shipped lines while keeping unshipped lines open.

• 1 Eligibility: Shipment syncs once the Accounting Order exists in NetSuite.
• 2 Create/Update: We create an Item Fulfillment and attach tracking.
• 3 Line association: Items are linked by SKU.

Multiple shipments are supported via partial fulfillments:

• Create a fulfillment for shipped lines (attach tracking on those lines).
• Leave unshipped lines unfulfilled in the same request (SO stays Partially Fulfilled).
• Later shipments create new fulfillments for the remaining lines.

• No fulfillment created → ensure the Accounting Order exists and template maps SKU + Quantity.
• Tracking on wrong line → verify SKU parity NetSuite ⇄ Flxpoint.
• Partial not reflected → unshipped lines must remain unfulfilled in that request.
• Transform error → include a valid inventoryLocation when transforming to Item Fulfillment.
• Automation → confirm the operation is Scheduled and saved.