For the complete documentation index, see llms.txt. This page is also available as Markdown.

Orders

Configure PO creation and numbering, required fields, auto-close, order confirmations, check-ins, and configurable fields on orders and line items

The Orders settings control how purchase orders are created, managed, and enriched with additional fields. The settings are split across three tabs:

  • General — order creation, numbering, and required fields

  • Order lifecycle — auto-close, order confirmations, change orders, receiving, and check-ins

  • Configurable fields — additional fields on orders and order line items

General

Order Creation & Numbering

These settings control how purchase orders are created and numbered:

Setting
Description

Order creation enabled

When enabled, users can create new purchase orders directly in Silkline. When disabled, order creation is blocked—this is typically used when POs are managed entirely through an external ERP system.

Use External System PO Numbers

When enabled, Silkline will use the PO number from your external integration instead of generating a Silkline PO number.

Order Number Prefix

Set a prefix for all Silkline-generated order numbers (e.g. "PO-" results in PO-001, PO-002).

Starting Order Number

Set the starting number for Silkline-generated order numbers. This is useful when migrating from another system.

Some settings can only be changed by Silkline support. Please reach out to us if you need assistance.

Order Settings

These settings control order behavior and requirements:

Setting
Description

Require Part Selection for Order Line Items

When enabled, all order line items must have a part selected before the order can be saved or submitted. This is helpful when external systems orders are synced to require a part for each line item.

Require Request & Order Rationale

When enabled, users must provide a justification or purpose for each request and order before submission. This is useful for approval routing and auditing.

Use Need Dates from Request by Default

When enabled, the "Use Need Dates from Request" toggle is on by default when creating an order from a quote linked to a request. Users can still change it on each order.

Disable Order-Level Adjustments

When enabled, adjustments cannot be added to the bottom of purchase orders. Value changes must be made at the line-item level. This is required for organizations with NetSuite or Ramp integrations.

Show Line Item ETA on PO PDF

When enabled, each line item's ETA is printed on purchase order PDFs. Turn it off to keep ETAs internal. The order page in Silkline always shows the ETA.

Note: The "Require Request & Order Rationale" setting also appears in the Requests section, as it controls the rationale requirement for both requests and orders.

Order Lifecycle

Auto-Close Orders

Setting
Description

Auto-Close Fully Received Orders

When enabled, an open order automatically moves to Closed once its receipt status reaches Complete.

Auto-Close Fully Billed Orders

When enabled, an open order automatically moves to Closed once its billed status reaches Billed.

Auto-close settings combine. If both "Auto-Close Fully Received Orders" and "Auto-Close Fully Billed Orders" are enabled, an order closes only once it is both fully received and fully billed. If only one is enabled, that condition alone is sufficient. If neither is enabled, orders are never closed automatically — closing remains a manual action.

Order Confirmations

Setting
Description

Check Order Emails for Confirmations

When enabled, Silkline automatically processes incoming order confirmation emails and matches them against open orders to validate supplier acknowledgements.

Require suppliers to sign in to confirm purchase orders

When enabled, suppliers can still view a purchase order from its share link, but must sign in to Silkline to confirm it or change a line item's status. The share link shows a Log in to confirm button in place of Confirm Purchase Order, and check-ins sent from a share link can update ETAs but not statuses.

Receiving

Setting
Description

Received quantities from receipts

Off by default, and turned on by Silkline. When enabled, an order line's received quantity is the total of its receipts, including reversals, and can't be edited by hand. A line with no receipts shows 0 received.

Check-ins

These settings control which order lines are included in check-ins:

Setting
Description

Exclude non-receivable lines from check-ins

On by default. When enabled, check-ins leave out order lines that aren't linked to a part and lines whose part is non-receivable, such as services or freight. Turn it off if your orders use description-only lines that suppliers need to report status on.

Configurable Fields

Order Configurable Fields

You can configure additional fields to appear on purchase orders. This helps standardize data capture across your organization and ensures orders include the information needed for approvals, fulfillment, and reporting.

There are two types of fields you can configure: Core Fields and Custom Fields.

Core Fields

Core fields are commonly used attributes on POs. You can enable and configure any combination of the following:

  • Bill To Address – The billing address that will appear on the PO.

  • Payment Terms – Predefined terms like Net 30 or Net 45.

  • Delivery Terms – Terms such as FOB/Incoterms.

  • Delivery Mode – Shipping method or delivery type (e.g. Ground, Air).

You can configure or edit these fields to set defaults that will apply to all new orders.

Ship-to addresses are managed as Locations, not as a configurable field.

Custom Fields

Custom fields let you tailor orders to capture organization-specific data. You can choose different field types, such as:

  • Text fields – For freeform entries (e.g. Project Name, Cost Code)

  • Select fields – For predefined dropdowns (e.g. Department, Budget Pool)

  • Multi-select fields – Similar to select fields, but allows multiple selections

  • Boolean fields – For simple Yes/No toggles (e.g. "Is Tax Exempt")

Common use cases for custom fields include:

  • Tracking budget codes or internal cost centers

  • Tracking attribute required for syncing to other systems

  • Identifying projects, programs, or departments

  • Flagging orders with special internal routing (e.g. CAPEX vs OPEX)

  • Adding internal classification fields for reporting

Order Item Configurable Fields

In addition to order-level fields, you can also configure fields for order line items. These allow you to capture structured data at the line level for better planning and tracking.

Core Fields

  • Need Date – Captures the required delivery date for each line item.

You can enable and configure this to standardize how due dates are captured.

Custom Fields

Just like at the order level, you can add custom text, select, or boolean fields to line items. This can be useful for:

  • Capturing line-level budget codes

  • Adding engineering or manufacturing references

  • Tagging special handling or inspection instructions

  • Tracking commodity or category information

See Configurable Fields for more details on creating and managing custom fields.

Last updated

Was this helpful?