(v1.0) LS Central customerOrder API (1.0.0)

Exposes the exchange rate for a currency Code. Provided as a read-only OData v4 entity replacing the generic RetailWebServices GET_TABLE_DATA read of table "Currency Exchange Rate". This release is read-only (Phase 1): Insert, Modify, and Delete are not supported over the API; exchange rates are maintained through the LS Central back-office UI. A future phase may add write support.

Exposes the per-store default Shipping Agent / Agent Service assignment — one row per store, plus a single fallback row with a blank storeNo that applies to all stores without their own row — as a read-only OData v4 entity. Replaces the legacy COShipAgentsInfoGet SOAP web service (codeunit LSCCOShipAgentsInfoGet / LSCCOShipAgentsInfoGetUtils), which returned every "LSC CO Default Shipping Agent" row, every Shipping Agent, and every Shipping Agent Service unfiltered in one payload. This entity is a simple flat projection: it returns only the storeNo/shippingAgentCode/agentServiceCode assignment, with no nested navigation. A consumer that needs the full Shipping Agent or Shipping Agent Service detail (name, internet address, account number, description, shipping time, etc.) makes a separate GET against the standalone LSC Shipping Agent API or LSC Shipping Agent Service API, filtering by the shippingAgentCode / agentServiceCode value returned here. This release is read-only: Insert, Modify, and Delete are not supported over the API; default shipping agent assignments are maintained through the LS Central back-office UI. The bound action resolveEffective(storeNo) implements the store-else-blank-fallback resolution used by the Customer Order POS session (Customer Order Session.GetShippingAgents): it looks for a row matching the given storeNo, and if none exists, falls back to the row with a blank storeNo; it errors if neither exists. This resolution logic is NEW, additive server-side convenience added by this API — the legacy SOAP operation itself performs no store filtering at all, so resolveEffective is not a byte-for-byte replication of legacy behavior. On success, the action repoints the response at the resolved defaultShippingAgent entity, so a caller can immediately GET it and then follow up with separate calls to LSC Shipping Agent API / LSC Shipping Agent Service API for the full detail.

Exposes Shipping Agent Services (standard table) — the shipping services offered by a shipping agent, including code, description, and expected shipping time — as a read-only OData v4 entity, nested under the parent shippingAgents entity. Replaces the legacy RetailWebServices GetShippingAgentService(agentId) operation (GetGeneralWebRequestXML("Shipping Agent Services", "Shipping Agent Code", agentId)), a per-agent read. This release is read-only: Insert, Modify, and Delete are not supported over the API; shipping agent services are maintained through the LS Central back-office UI.

Exposes the store/item/variant scoped return policy rules — whether refunds are allowed, what manager privileges are required, the allowed refund period, and the messages shown to the customer — as a read-only OData v4 entity. Replaces the legacy GetReturnPolicy SOAP web service (codeunit LSCGetReturnPolicyUtils and the GetReturnPolicyXML xmlport), which callers queried by supplying explicit Store No. / Store Group Code / Item Category Code / Retail Product Code / Item No. / Variant Code / Variant Dimension 1 Code parameters, with a blank parameter meaning wildcard. This API reproduces that same scoping behavior declaratively: filter on storeNo, storeGroupCode, itemCategoryCode, retailProductCode, itemNo, variantCode, and variantDimension1Code — all plain, independently filterable OData columns — to retrieve exactly the return policies that would have matched the equivalent SOAP request. This release is read-only (Phase 1): Insert, Modify, and Delete are not supported over the API; return policies are maintained through the LS Central back-office UI. A future phase may add write support.

Exposes posted Sales Shipment Header records as an OData v4 entity, replacing the legacy SOAP operations SalesShipmentListGet and SalesShipmentUpdate (18-month guaranteed coexistence — the legacy web service is untouched). This release supports GET and PATCH only; there are no bound or unbound actions. Only shippingAgentCode, shippingAgentServiceCode, and packageTrackingNo are writable, matching the legacy SalesShipmentUpdate operation''s parity exactly — no other field may be patched. lscCustomerOrderId can be used as an OData filter to scope the results to the shipments of one Customer Order document, mirroring the legacy operation''s own DocumentID-scoped read.

Exposes Shipping Agent (standard table) master data — code, name, internet address, and account number — as a read-only OData v4 entity. Replaces the legacy RetailWebServices ReplicateShippingAgent(...) operation (GetGeneralWebRequestXML("Shipping Agent"), a full unfiltered read). The nested shippingAgentServices part replaces the per-agent GetShippingAgentService(agentId) call. This release is read-only: Insert, Modify, and Delete are not supported over the API; shipping agents are maintained through the LS Central back-office UI.