SyteLine Ecommerce Integration and B2B Portals

B2B Ecommerce Portals and Web Stores for Infor SyteLine

Short answer

Manufacturers selling direct-to-customer or through B2B portals need real-time synchronization between their e-commerce platform and SyteLine. Orders placed online must flow into SLCos, inventory availability from SLWhseitems must reflect on product pages, and shipping confirmations from SLShipments must update customer-facing order status. Without reliable e-commerce integration, manufacturers face overselling, manual data entry backlogs, and poor customer experience.

Order and Customer Data Synchronization

Inbound order sync is the most critical integration path. When a customer places an order on Shopify, Magento, or WooCommerce, the integration must create a customer order (SLCos), populate line items (SLCoitems), resolve or create the customer record (SLCustomers), and set the correct ship-to address (SLCustaddr). Order acknowledgment flows back to the e-commerce platform to confirm receipt and provide an estimated ship date.

Webhook-triggered order sync from Shopify/Magento to SLCos via REST API with sub-second processing
Customer resolution logic: match by email in SLCustomers, create new customer record if no match found
Map e-commerce line items to SLCoitems using SKU-to-item cross-reference in SLItemCustXref table
Populate SLCustaddr with shipping address, creating new ship-to records when address is not on file
Return order confirmation with SyteLine CO number and estimated ship date to the e-commerce platform

Inventory and Pricing Synchronization

Real-time inventory availability prevents overselling by pushing SyteLine's on-hand quantities from SLWhseitems to the e-commerce product catalog. Pricing sync ensures that price list changes in SLItemprice reflect immediately on the storefront. For B2B scenarios, customer-specific pricing from SLCustPrice must be resolved at login and applied to the customer's session.

Push inventory updates from SLWhseitems.qty_on_hand to e-commerce on inventory transaction events via ION
Calculate available-to-promise (ATP) from SLWhseitems considering allocations, safety stock, and in-transit quantities
Sync price list changes from SLItemprice to e-commerce catalog via scheduled batch or event-driven updates
Implement B2B customer-specific pricing by querying SLCustPrice IDO on customer login and caching per session
Handle multi-warehouse scenarios by aggregating availability across SLWhseitems rows for the same item

Shipping, Returns, and Post-Order Workflows

After SyteLine processes and ships an order, the shipment confirmation from SLShipments with carrier tracking information must flow back to the e-commerce platform for customer notification. Returns initiated on the e-commerce side must create RMA records in SyteLine via SLRmas and SLRmaItems, triggering the returns receiving and credit memo workflow.

Push shipment confirmation from SLShipments with tracking number and carrier code to e-commerce order status
Map SyteLine pack/ship events to Shopify Fulfillment API or Magento Shipment API for customer notification
Create SLRmas and SLRmaItems from e-commerce return requests with reason codes and return authorization numbers
Sync credit memo generation from SLCrMemoHdr back to e-commerce for refund processing
Implement order status webhook that queries SyteLine co.stat and ships updates to e-commerce order timeline

Try it here, free

SyteLine Job and Order Status Codes Reference

Open full tool

Look up what Planned, Firm Planned, Released, Stopped, Complete and the other SyteLine status codes mean and how they behave in planning and shipping.

Download:

Object	Stat code	Status name	What it means	Planning and MRP behavior	Typical next step
Job	P	Planned	Job exists as a proposal, often created by planning or entered as a draft.	MRP and APS can change or replace it. Not yet a firm commitment.	Firm or release it when the order is real.
Job	F	Firm Planned	Job is held fixed against replanning but is not yet on the shop floor.	Planning leaves quantity and dates alone and treats the demand it creates as firm.	Release when materials and capacity are confirmed.
Job	R	Released	Job is open on the shop floor and can receive material issues, labor and move transactions.	Counts as supply for its parent item and as demand for unissued components.	Report production, then complete.
Job	S	Stopped	Job is paused. Transactions are blocked until it is released again.	Still visible to planning, so open supply may be overstated while it is stopped.	Resolve the issue and return to Released, or cancel.
Job	C	Complete	Job is closed to further production transactions.	No longer counts as supply or component demand.	Run job cost close and review variances.
Customer order	P	Planned	Quote-like order held as a draft, not committed to the customer.	Normally excluded from firm demand unless your planning settings include it.	Convert to Ordered when confirmed.
Customer order	O	Ordered	Confirmed order that is open and can be picked, shipped and invoiced.	Lines drive demand into MRP and reserve inventory.	Pick, pack and ship.
Customer order	S	Stopped	Order is held, for example for credit or customer request.	Shipments are blocked while the order is stopped.	Clear the hold or cancel.
Customer order	F	Filled	All lines are fully shipped but the order is not yet closed out.	No remaining demand.	Invoice remaining shipments and complete.
Customer order	C	Complete	Order is shipped, invoiced and closed.	No remaining demand.	Archive per retention policy.
Customer order line	O	Ordered	Line is open with quantity still to ship.	Quantity ordered less shipped is net demand.	Ship against it.
Customer order line	F	Filled	Line quantity has been shipped in full.	No remaining demand for this line.	Invoice and complete.
Customer order line	C	Complete	Line is shipped and invoiced.	No remaining demand.	None.
Purchase order	P	Planned	Draft PO, not yet released to the supplier.	May be treated as planned supply depending on your settings.	Approve and place the order.
Purchase order	O	Ordered	Placed with the supplier and awaiting receipt.	Counts as firm supply on its due date.	Receive against it.
Purchase order	F	Filled	All lines are received in full.	No remaining supply.	Match to the supplier invoice.
Purchase order	C	Complete	PO is received, matched and closed.	No remaining supply.	None.

Codes are the values commonly stored in the stat column of the job, co, coitem, po and poitem tables. Labels and which statuses are available can vary by SyteLine version and by your site settings, so confirm against the status lists in your own forms before building reports or integrations on them.

Status-aware SyteLine questions

Optional: see how a read-only assistant answers questions such as stale firm planned jobs directly from your SyteLine data.

Optional. The tool and every export work without this. No spam.

Connect your e-commerce platform to SyteLine seamlessly: Netray's integration agents handle the complexity. Request a demo.

Talk to an engineer Try the free SyteLine Job and Order Status Codes Reference

Object

Stat code

Status name

What it means

Planning and MRP behavior

Typical next step

Job

Planned

Job exists as a proposal, often created by planning or entered as a draft.

MRP and APS can change or replace it. Not yet a firm commitment.

Firm or release it when the order is real.

Job

Firm Planned

Job is held fixed against replanning but is not yet on the shop floor.

Planning leaves quantity and dates alone and treats the demand it creates as firm.

Release when materials and capacity are confirmed.

Job

Released

Job is open on the shop floor and can receive material issues, labor and move transactions.

Counts as supply for its parent item and as demand for unissued components.

Report production, then complete.

Job

Stopped

Job is paused. Transactions are blocked until it is released again.

Still visible to planning, so open supply may be overstated while it is stopped.

Resolve the issue and return to Released, or cancel.

Job

Complete

Job is closed to further production transactions.

No longer counts as supply or component demand.

Run job cost close and review variances.

Customer order

Planned

Quote-like order held as a draft, not committed to the customer.

Normally excluded from firm demand unless your planning settings include it.

Convert to Ordered when confirmed.

Customer order

Ordered

Confirmed order that is open and can be picked, shipped and invoiced.

Lines drive demand into MRP and reserve inventory.

Pick, pack and ship.

Customer order

Stopped

Order is held, for example for credit or customer request.

Shipments are blocked while the order is stopped.

Clear the hold or cancel.

Customer order

Filled

All lines are fully shipped but the order is not yet closed out.

No remaining demand.

Invoice remaining shipments and complete.

Customer order

Complete

Order is shipped, invoiced and closed.

No remaining demand.

Archive per retention policy.

Customer order line

Ordered

Line is open with quantity still to ship.

Quantity ordered less shipped is net demand.

Ship against it.

Customer order line

Filled

Line quantity has been shipped in full.

No remaining demand for this line.

Invoice and complete.

Customer order line

Complete

Line is shipped and invoiced.

No remaining demand.

None.

Purchase order

Planned

Draft PO, not yet released to the supplier.

May be treated as planned supply depending on your settings.

Approve and place the order.

Purchase order

Ordered

Placed with the supplier and awaiting receipt.

Counts as firm supply on its due date.

Receive against it.

Purchase order

Filled

All lines are received in full.

No remaining supply.

Match to the supplier invoice.

Purchase order

Complete

PO is received, matched and closed.

No remaining supply.

None.

B2B Ecommerce Portals and Web Stores for Infor SyteLine

Order and Customer Data Synchronization

Inventory and Pricing Synchronization

Shipping, Returns, and Post-Order Workflows

Status-aware SyteLine questions

Keep exploring

Free tools

Runs with your ERP

Guides

AI on your ERP

Status-aware SyteLine questions