API package
Supply Chain
Items, suppliers, purchasing, bin-level inventory, and warehouse execution. Receipts accrue GR/IR in Accounting.
208 APIs1511 operationsBase path
/api/scmAutomation
Buying
Catalogs
Hosted and punch-out catalogs, priced from the contract behind them.
GET3 POST3 PUT2 DELETE2
Guided Buying
What a person may buy without asking, when quotes or a sourcing event are required, and where to buy it from. Ask the guide rather than a colleague.
GET2 POST2 PUT1 DELETE1
Service Receipt
A service is received by confirming it happened. Approval accrues the cost, so the ledger knows about work done before the invoice arrives.
GET2 POST5 PUT1 DELETE1
Capacity & Scheduling
Capacity Calendars
When a resource is actually available. Shifts, holidays, planned maintenance, a second crew on Saturday. One row per day, because the exception is the point.
GET2 POST2 PUT1 DELETE1
Capacity Load
What a plan asks of a resource in a period against what it has. The row a finite run reads before it dares to schedule anything into a period.
GET2 POST2 PUT1 DELETE1
Capacity Resources
Anything with a finite amount of time in it: a work center, a crew, a vehicle, a driver. One list for all of them, because a factory whose bottleneck is its delivery fleet is a real and common situation.
GET3 POST3 PUT2 DELETE2
Capacity Schedules
One board: this set of resources, over this window. A factory schedule, a work center schedule and a vehicle schedule are the same document with a different resource kind on it.
GET3 POST5 PUT2 DELETE2
Collaboration
Order Confirmations
What was asked for beside what the supplier promised, so the gap is visible without chasing it.
GET2 POST4 PUT1 DELETE1
Shipping Notices
What the supplier says is on its way. Receiving one stages a goods receipt, so it arrives the same way as anything else.
GET3 POST4 PUT2 DELETE2
Supplier Collaboration
The conversation, against the document it is about. Whose turn it is follows from who spoke last.
GET3 POST4 PUT2 DELETE2
Contract Management
Contract Templates
The standard wording, with merge fields the authoring step fills in.
GET2 POST2 PUT1 DELETE1
Contracts
Authored from a template, held in one place, and enforced: the prices a contract fixes are what a purchase is checked against.
GET5 POST7 PUT4 DELETE4
Demand Planning
Demand Forecast Lines
One item, one place, one period. Five quantities, because the statistical number, what sales think, what marketing think, what was agreed and what happened are five different facts.
GET2 POST2 PUT1 DELETE1
Demand Plans
A named, dated statement of what is expected. Versioned rather than overwritten: last month plan is what this month accuracy is measured against, and editing one in place destroys the only evidence anybody has.
GET3 POST9 PUT2 DELETE2
Demand Signals
Demand that is not a forecast: a signed order, a likely quotation, a weighted opportunity, a dependent requirement. One place for a planning run to read demand from, and it can say where every unit came from.
GET2 POST3 PUT1 DELETE1
Forecast Accuracy
Was the forecast any good. Which items are forecastable at all is usually a more useful answer than a better model.
GET2 POST2 PUT1 DELETE1
Forecast Models
How a statistical forecast is calculated. Held as data so a planner can add one without a deployment, and so a run can record which it used.
GET2 POST2 PUT1 DELETE1
Direct Materials
Scheduling Agreements
A long-running commitment to one supplier for one material. Releasing against the schedule raises a real purchase order, and cannot exceed what was agreed.
GET3 POST4 PUT2 DELETE2
Supplier Forecasts
What the supplier has been told to expect, what they committed to, and what actually happened.
GET2 POST3 PUT1 DELETE1
Dock Scheduling
Dock Appointments
Carrier bookings of a door and a slot — a gate entry for a delivery: what is coming or going, against which order or notice, how many pallets — and when the truck actually arrived. A door cannot be booked twice for the same time.
GET3 POST7 PUT1 DELETE1
Dock Board
One warehouse, one day: doors down, slots across, every booking in its cells — check trucks in, send them to the door and check them out from here.
GET1
Dock Calendars
Per warehouse: how long a slot is, when the dock opens and closes and on which days, how late is late, when a booking becomes a no-show, and whether carriers may book themselves.
GET2 POST2 PUT1 DELETE1
Dock Closures
A door, or the whole dock, shut for a holiday or maintenance. No slot inside a closure can be booked.
GET2 POST2 PUT1 DELETE1
Drop-Ship
Drop-Ship Confirmations
Every time a vendor said a drop-ship order had gone — from the console, the supplier portal or an 856 — with the pass-through receipt, the cost journal and the customer invoice it made.
GET3 POST4 PUT2 DELETE2
Drop-Ship Orders
Sales order lines the vendor ships straight to the customer: the vendor order behind each, and how far it has got. Nothing here touches your own stock.
GET2 POST4 PUT1 DELETE1
Electronic Data Interchange
EDI Connectors
How files travel: AS2, SFTP, a VAN mailbox — or the sandbox, which keeps every file on its interchange to download. Credentials are stored sealed and never shown.
GET2 POST3 PUT2 DELETE1
EDI Document Maps
Per partner and document: inbound or outbound, what it makes or is made from, how items are named, and whether an inbound document is processed on arrival or held for review.
GET2 POST2 PUT1 DELETE1
EDI Interchanges
Every interchange sent or received: the control numbers, the status, the acknowledgement, the faults in sentences, the documents it made, and the file exactly as it was.
GET4 POST7 PUT1 DELETE1
EDI Partners
The customers, suppliers and carriers you exchange EDI with: X12 004010/005010 or EDIFACT D96A/D01B, the interchange IDs and qualifiers on both sides, the separators, and how files travel.
GET2 POST2 PUT1 DELETE1
Freight Forwarding
Containers
The box itself. A container without a verified gross mass does not get loaded, which is why that is a column rather than a note.
GET2 POST2 PUT1 DELETE1
Customs Declarations
The customs entry, held as its own document because it has its own number, its own dates, its own duty and its own way of going wrong.
GET3 POST3 PUT2 DELETE2
Forwarding Shipments
A house bill under a master bill. A forwarder makes its money on the spread between what it buys at and what it sells at, so buy and sell are two columns rather than one.
GET5 POST4 PUT3 DELETE3
Freight Charges
The priced detail: linehaul, fuel, each accessorial, on its own line. Both what it was bought at and what it is sold at, because the difference is the whole business model of a forwarder.
GET2 POST2 PUT1 DELETE1
Freight Management
Accessorial Charges
What a carrier charges for beyond moving the goods. Half a freight bill is usually these, and an accrual that ignores them is wrong by half.
GET2 POST2 PUT1 DELETE1
Carrier Scorecard
Computed rather than typed: what each carrier moved, what it cost, how much of it arrived on time, and how often their invoice was wrong.
GET2 POST2 PUT1 DELETE1
Carrier Services
What a carrier sells. "UPS" is not a service; "UPS 2nd Day Air" is, and it is the thing that has a transit time and a cutoff.
GET2 POST2 PUT1 DELETE1
Carriers
Who moves it. A carrier IS a supplier as far as payables is concerned, so a freight invoice posts against the supplier record rather than into a second ledger.
GET2 POST2 PUT1 DELETE1
Freight Classes
The NMFC scale. Density, stowability, handling and liability decide it, and it is the single biggest driver of an LTL price.
GET2 POST2 PUT1 DELETE1
Freight Orders
The instruction to a carrier: collect here, deliver there, these stops in this order. Tendered, accepted, refused, offered to the next one down.
GET5 POST6 PUT3 DELETE3
Freight Tariffs
A price agreement with a carrier. The rate basis is what lets one engine price parcel, LTL and truckload: three different arithmetics, one lane comparison.
GET3 POST3 PUT2 DELETE2
Rate Shopping
What came back when several carriers were asked. Kept rather than thrown away: "why did we ship this on the expensive one" is a question somebody asks three weeks later.
GET3 POST3 PUT2 DELETE2
Routes
The drawn line and the plan behind it. Sequencing the stops is nearest-neighbour with time windows pulling a stop forward: crude, fast, and typically within a fifth of optimal on a delivery round.
GET2 POST3 PUT1 DELETE1
Tracking Events
What the carrier told us, when. The evidence behind an on-time-delivery figure, normalized so a dashboard does not have to know that UPS says "I" and FedEx says "IT".
GET2 POST2 PUT1 DELETE1
Transport Lanes
Origin region to destination region, by mode. The unit a rate is quoted on and the unit a spend analysis is done on.
GET2 POST2 PUT1 DELETE1
Freight Settlement
Goods Movement
Image Capture
What a vision model was asked and what it answered, with how long it took and how confident it was. Kept so a reading can be challenged.
GET2 POST2 PUT1 DELETE1
Item Barcodes
What is printed on the goods. A code is checked against its own check digit before it is stored, so a scan that fails later was wrong on the label.
GET2 POST2 PUT1 DELETE1
Movement History
One movement in progress. Scan a barcode, wave a tag or photograph the pallet; the platform decodes it, checks it and posts it. Every kind of movement is the same three steps.
GET3 POST8 PUT2 DELETE2
RFID Readers
Where tags are read: dock portals, handhelds, shelves and conveyors.
GET2 POST2 PUT1 DELETE1
RFID Tags
Every tag, what it is attached to, and where it was last seen. An EPC decodes to the GTIN and serial inside it.
GET2 POST2 PUT1 DELETE1
Inventory Costing
Cost Layers
Each receipt of a FIFO or LIFO item, what is left of it and what a unit of it costs now (landed cost included).
GET2 POST2 PUT1 DELETE1
Cost Revaluations
Re-prices an item’s stock and, if you wish, changes its costing method. Open layers are closed, stock restarts under the new method at the unit cost you give, and the difference is posted to inventory against the inventory adjustment account.
GET2 POST2 PUT1 DELETE1
Costing Method Changes
Every time an item’s costing method changed, and whether a cost revaluation made the change.
GET2 POST2 PUT1 DELETE1
Inventory Valuation
What stock is worth, item by item, by the costing method each item is costed with — beside what it would be worth at standard cost.
GET2 POST2 PUT1 DELETE1
Inventory Structure
Invoices & Payment
Invoice Capture
An invoice however it arrived — scanned, emailed, EDI or keyed. Capture finds the supplier and the order, and flags a duplicate before it becomes a double payment.
GET2 POST5 PUT1 DELETE1
Match Results
What each match compared and what it found. An exception is released by a person, with a reason on the record.
GET2 POST3 PUT1 DELETE1
Payment Proposals
What is due by a date, what discount is lost by waiting, and what to pay. Releasing it becomes a bank payment batch rather than a second way of paying.
GET3 POST6 PUT2 DELETE2
Payment Terms
When an invoice is due and the cash discount for paying early. A term can have several lines — discount tiers, a fixed day of the month, a baseline date, a different rule for invoices dated after the 15th. Orders, invoices and payment proposals follow them.
GET2 POST2 PUT1 DELETE1
Items & Suppliers
Items
Open an item and everything about it is there: its organizations, sales, purchasing, planning, work definition, revisions, stocking, quality, costing and lot control, each one dated so you can read it as it stood on any day.
GET7 POST4 PUT2 DELETE2
Quota Arrangements
For each item, how its demand is split between suppliers, in which part of the company and for what period. A requisition line that names no vendor is proposed the supplier furthest below its share: the one whose allocated quantity plus the line’s, divided by its share, is lowest. Shares in force at the same time may add up to 100% at most. Quota arrangements are asked first; then the Source List’s fixed source, an outline agreement (Contracts), and the item’s Purchasing record.
GET2 POST2 PUT1 DELETE1
Source List
For each item, which suppliers it may be bought from, in which part of the company and for what period. A blocked supplier is refused on purchase orders for the item. The fixed source is the supplier a requisition line takes when nobody names one, and its Purchasing record prices the line. Where the item’s Purchasing record says “Source list required”, only the suppliers listed here may be ordered from.
GET2 POST2 PUT1 DELETE1
Suppliers
Open a supplier for its sites, financial terms, bank details, certifications, diversity and exclusions — the ordering address is almost never the one you pay.
GET4 POST3 PUT1 DELETE1
Load Building
Drivers
Who drives. The hours are the point: a driver out of hours is a load that does not go, and scheduling a run that breaks the rules is the most expensive mistake a transport planner can make.
GET2 POST2 PUT1 DELETE1
Loads
One vehicle worth of freight. Utilization is the whole point: a trailer at sixty per cent is forty per cent of the freight bill spent carrying air.
GET5 POST8 PUT3 DELETE3
Vehicle Types
The kinds of vehicle a plan may use. The inside dimensions are the load builder’s canvas: it draws exactly that rectangle and fits pallets into it.
GET2 POST2 PUT1 DELETE1
Vehicles
One actual vehicle, owned, leased or the carrier’s. The compliance dates sit on the master because each of them expiring grounds it.
GET2 POST2 PUT1 DELETE1
Maps & Geography
Geofences
An area on the map that means something: a customer site, a depot yard, a low emission zone. Crossing one says the truck has arrived without anybody telephoning to ask.
GET2 POST2 PUT1 DELETE1
Mapping Providers
Which mapping service this company uses. OpenStreetMap needs no key and no account, so the map draws on the first boot; a Google or Mapbox contract is added here.
GET2 POST2 PUT1 DELETE1
Places
A place, geocoded. Held once and referenced everywhere: the same customer address appears on a hundred deliveries, and correcting it once should correct all of them.
GET2 POST2 PUT1 DELETE1
Network
Bins
Read and maintain bins records (scm.bins).
GET2 POST2 PUT1 DELETE1
Lanes
Read and maintain lanes records (scm.lanes).
GET2 POST2 PUT1 DELETE1
Locations
Read and maintain locations records (core.locations).
GET2 POST2 PUT1 DELETE1
Shelves
Read and maintain shelves records (scm.shelves).
GET2 POST2 PUT1 DELETE1
Warehouses
Read and maintain warehouses records (scm.warehouses).
GET3 POST2 PUT1 DELETE1
Procurement Control
Approval Levels
The people a rule asks to sign, one level at a time, in order. A level whose approver has left or is on leave is skipped and the next one fills it; a level that must be filled by somebody holds the document instead. Works the same way for a purchase order and for a requisition, because it is one policy.
GET2 POST2 PUT1 DELETE1
Material at Subcontractors
What the company owns and is not holding: material issued to a subcontractor, what they consumed, returned and spoiled, and what is still out there.
GET2 POST4 PUT1 DELETE1
Procurement Exceptions
Everything between a customer order and the material it needs that is not moving — unapproved requisitions, unawarded tenders, late deliveries, rejected material, overdue subcontractors and invoices that will not match.
GET2 POST2 PUT1 DELETE1
Requisition Approval Rules
Which purchase requisitions need a signature, and whose. The same shape a purchase order rule has, because a company should express its delegation of authority once.
GET3 POST3 PUT1 DELETE1
Requisition Approvals
Every signature a requisition is waiting for, oldest first. A requisition may not become a purchase order until they are all in — and the database, not a screen, is what enforces that.
GET2 POST3 PUT1 DELETE1
Vendor Evaluation Criteria
What responses will be compared on, and how much each counts — declared before any response is opened. Criteria chosen afterwards are criteria chosen to fit the preferred answer.
GET2 POST2 PUT1 DELETE1
Vendor Evaluation Scores
What each vendor scored on each criterion, and what it was worth once weighted. Price, lead time and payment terms are each scored against the best response: the lowest offer, the shortest lead time, the longest credit. Unless the event says otherwise they weigh 60%, 20% and 20%.
GET2 POST2 PUT1 DELETE1
Product Configurator
Configurations
What customers actually configured, what it came to, and whether it can be made yet.
GET9 POST8 PUT1 DELETE1
Configurator · Models
A configurable product and how a configuration of it gets made — configure, assemble, make or engineer to order.
GET4 POST4 PUT3 DELETE3
Configurator · Options
The answers. An option with an item puts a part in the product; one without is a characteristic that changes price and paperwork.
GET2 POST2 PUT1 DELETE1
Configurator · Parameters
The named constants a calculation rule leans on — the process allowance, the cutting allowance, a density. Named so a formula reads as a sentence rather than as arithmetic over numbers nobody can place.
GET2 POST2 PUT1 DELETE1
Configurator · Questions
The questions a model asks, in order. How many answers each takes decides whether it is a radio button or a checklist.
GET2 POST2 PUT1 DELETE1
Configurator · Rules
Two kinds of rule in one list. CONSTRAINT rules say what may be chosen, as explicit pairs, because a rule has to be explicable to a salesperson standing in front of a customer. PROCESS rules say what the choice MEANS — which component, in what quantity, through which operation, with which inspection — and carry a condition written in the ordinary expression language.
GET4 POST5 PUT2 PATCH1 DELETE2
Configurator · Sub-assembly Inheritance
Which of a parent model’s answers travel down to a child model, and under what name there. Without the map a sub-assembly is configured in isolation, and a 12 mm machine acquires a 10 mm axle.
GET2 POST2 PUT1 DELETE1
Configurator · Workbook
The whole definition of a configurable product — models, characteristics, values, rules written as IF … THEN … sentences, components, operations and sub-assembly structure — as one Excel workbook to download, edit and upload; or many rules pasted as text at once.
GET1 POST1
Configured · Components
Every part the rules put in a configuration, at the quantity their formulas computed, with the rule that chose it. The answer to “why does this order have this part”.
GET2 POST2 PUT1 DELETE1
Configured · Cost Sheet
The rolled-up cost of a configuration, element by element — material, labour, machine, setup, outside processing, scrap, freight, packaging and overhead. A total nobody can check is a total nobody can defend.
GET2 POST2 PUT1 DELETE1
Configured · Inspections
The inspections a configuration’s characteristics decided on — incoming, in-process and final. The same rules that chose the parts choose what is measured.
GET2 POST2 PUT1 DELETE1
Configured · Routing
The operations a configuration resolved to, in sequence, with the work centre, the time the rules computed and what each costs. A galvanizing operation that is not there is the answer to “why is this one cheaper”.
GET2 POST2 PUT1 DELETE1
Configured · Why
Every fact about one configuration in one list: what was answered, what was computed from it, what that selected, and which rule did it. The screen a production engineer opens when an operator asks why the traveller says what it says.
GET2 POST2 PUT1 DELETE1
Purchase Charges
Purchase Charge Conditions
The conditions of the purchase order pricing procedure (PO-STD): the gross price, discounts and surcharges, the charges (freight, packing and forwarding, insurance, inspection, customs duty and the Social Welfare Surcharge) and the GST heads. Each charge says whether the supplier bills it or somebody else is paid, its SAC code for GST, its GL account and which landed cost charge it becomes on receipt. Liquidated damages (LD): 0.5% of the late goods’ net value for every week late, at most 5% of the order’s net value, no VAT/GST, found for an order by its own condition records.
GET2 POST2 PUT1 DELETE1
Purchase Charge Records
The values: 5% off this supplier's orders, 20 a unit off this item, freight of 500 on every order, customs duty at 10% and the Social Welfare Surcharge at 10% on an importer's goods. The condition's access sequence decides which record applies to each line.
GET2 POST2 PUT1 DELETE1
Purchase Order Charges
Every charge a purchase order carries: those worked out from the charge records (again whenever its lines change, until goods are received) and those added by hand. Billed charges are in the order’s total; accrued ones are what its receipt’s landed cost is estimated from.
GET2 POST2 PUT1 DELETE1
Purchase Order Types
Reachable by link
Customs Lines
The tariff lines of a declaration: what it is, what it is classified under, where it came from, and what is owed on it.
GET2 POST2 PUT1 DELETE1
Freight Invoice Lines
Line by line against what was agreed, naming which of the seven ways a freight bill goes wrong this one is.
GET2 POST2 PUT1 DELETE1
Freight Order Lines
What is on the freight order as the carrier is told it: twelve pallets, 4,800 kg, class 70. Not the contents of each.
GET2 POST2 PUT1 DELETE1
Item · Costing
The cost method, the elements that make up the standard, and where it posts. The elements must add up to the standard — the platform refuses a row where they do not.
GET2 POST2 PUT1 DELETE1
Item · Engineering Revisions
What changed, when it took effect, what authorized it, and what happens to the stock that already exists. Geometry links to the model viewer.
GET2 POST2 PUT1 DELETE1
Item · Lot & Serial Control
The POLICY. Whether lots and serials are demanded, how they are formed, and what may not move without them — which is what turns traceability from an intention into a control.
GET2 POST2 PUT1 DELETE1
Item · Organizations
Which plants and business units an item is defined in. An item not assigned to an organization cannot be transacted there — that is the control.
GET2 POST2 PUT1 DELETE1
Item · Planning
How supply is decided and how demand is read — both sides in one row, because the planning run reads them together.
GET2 POST2 PUT1 DELETE1
Item · Purchasing
Who it is bought from, on what terms, with what tolerance, and how the invoice is matched.
GET2 POST2 PUT1 DELETE1
Item · Quality
When it is inspected, against what, and what happens when it fails. The flags here are what turn a receipt into quarantine.
GET2 POST2 PUT1 DELETE1
Item · Sales
What may be ordered, at what price, promised how, and invoiced when.
GET2 POST2 PUT1 DELETE1
Item · Stocking Policy
Where an item may be stocked and how it is restocked there — which is a different question from how the item is planned.
GET2 POST2 PUT1 DELETE1
Item · Warehouse
Dimensions, packing, putaway and picking — what the physical handling of the thing needs to know, as distinct from what planning needs.
GET2 POST2 PUT1 DELETE1
Item · Work Definition
How it is built: the bill of material and routing it is built against, the lot sizes, the yield and how components are consumed.
GET2 POST2 PUT1 DELETE1
Load Stops
Where the vehicle stops, in order. The sequence decides the loading order, because the first delivery has to be at the back of the trailer.
GET2 POST2 PUT1 DELETE1
On the Deck
One thing on the vehicle, and where it sits. The coordinates are what make the axle calculation and the picture the same fact.
GET2 POST2 PUT1 DELETE1
Quote Options
What each carrier said, and the arithmetic behind it. Kept so a disputed rate can be replayed.
GET2 POST2 PUT1 DELETE1
Rate Bands
One band of a tariff: between 500 and 1,000 kg, class 70, zone 4, this much per kg with a minimum.
GET2 POST2 PUT1 DELETE1
Schedule Entries
One bar on the Gantt. What makes it a schedule rather than a calendar is the dependency: operation 20 cannot start before operation 10 has finished.
GET2 POST2 PUT1 DELETE1
Slotting Recommendations
Where each item ought to move to, and why. Accepting one raises the move; rejecting one records that somebody looked.
GET2 POST3 PUT1 DELETE1
Supplier · Bank Details
Where the money goes. Changing any identifier resets the verification — an emailed "we have changed our bank" is the commonest fraud there is.
GET2 POST2 PUT1 DELETE1
Supplier · Buying Context
What each business unit is allowed to do with this supplier, and until when the approval lasts.
GET2 POST2 PUT1 DELETE1
Supplier · Certifications
What the supplier holds that lets us use them, its scope, and what happens when it lapses. The status follows the dates rather than being typed.
GET2 POST2 PUT1 DELETE1
Supplier · Diversity
Classification and the evidence behind it. Self-declared and third-party certified are different evidence, and spend reporting that conflates them will not survive an audit.
GET2 POST2 PUT1 DELETE1
Supplier · Exclusions
Reasons a supplier may not be used, and exactly what each one blocks. Distinct from diversity on purpose: one is a preference, this is a control.
GET2 POST2 PUT1 DELETE1
Supplier · Financial
Payment method, matching tolerance, withholding and the hold flag — at supplier level, or overridden per site.
GET2 POST2 PUT1 DELETE1
Supplier Sites
One supplier, several places: where invoices come from (billing), where the goods leave from (shipping), where the payment goes and where orders are sent. Purposes are independent ticks because one address is very often several of them.
GET2 POST2 PUT1 DELETE1
Records
Delegation
Read and maintain delegation records (scm.approval_delegations).
GET2 POST2 PUT1 DELETE1
Rfx documents
Read and maintain rfx documents records (scm.rfx_documents).
GET2 POST2 PUT1 DELETE1
Wave demand line
Read and maintain wave demand line records (scm.wave_demand).
GET2 POST2 PUT1 DELETE1
Reporting
Requisitions & Orders
Goods Receipts
Every goods receipt posted against a purchase order: what came in, into which bin, and the serial numbers of the units. Open a receipt and use “Register serials” on a line to record them — after posting too.
GET4 POST5 PUT3 DELETE3
PO Approval Rules
Which purchase orders need approval, and who signs. A rule on the buyer's reporting line follows the HRMS Organization Chart (and the position tree where a manager is not recorded), so reorganising the company re-routes approvals with nothing to change here.
GET4 POST4 PUT2 DELETE2
PO Approvals
Every signature a purchase order is waiting for, in the order they are collected. An order is received only once every level has approved.
GET2 POST3 PUT1 DELETE1
Purchase Orders
Read and maintain purchase orders records (scm.purchase_orders).
GET9 POST8 PUT2 DELETE2
Requisitions
Read and maintain requisitions records (scm.requisitions).
GET8 POST8 PUT2 DELETE2
Returns
Services and actions
Assets
The assets service of Supply Chain: 5 operation(s).
GET3 POST2
Contract price check
The contract price check service of Supply Chain: 1 operation(s).
GET1
Freight
The freight service of Supply Chain: 1 operation(s).
POST1
Geo
The geo service of Supply Chain: 2 operation(s).
POST2
Gst
The gst service of Supply Chain: 2 operation(s).
GET2
Guided buying
The guided buying service of Supply Chain: 1 operation(s).
POST1
Inventory
The inventory service of Supply Chain: 2 operation(s).
POST2
Labels
The labels service of Supply Chain: 1 operation(s).
POST1
Models
The models service of Supply Chain: 2 operation(s).
GET2
Movement
The movement service of Supply Chain: 10 operation(s).
GET6 POST4
Packing
The packing service of Supply Chain: 1 operation(s).
POST1
Planning
The planning service of Supply Chain: 1 operation(s).
GET1
Putaway
The putaway service of Supply Chain: 1 operation(s).
POST1
Recommendations
The recommendations service of Supply Chain: 1 operation(s).
GET1
Replenishment
The replenishment service of Supply Chain: 1 operation(s).
POST1
Rfid
The rfid service of Supply Chain: 1 operation(s).
POST1
Rfx derivable
The rfx derivable service of Supply Chain: 1 operation(s).
GET1
Rfx derive
The rfx derive service of Supply Chain: 1 operation(s).
POST1
Scan
The scan service of Supply Chain: 1 operation(s).
POST1
Slotting
The slotting service of Supply Chain: 1 operation(s).
POST1
Transport
The transport service of Supply Chain: 2 operation(s).
GET2
Uom
The uom service of Supply Chain: 1 operation(s).
POST1
Stock & Counts
Cycle Counts
Read and maintain cycle counts records (scm.cycle_counts).
GET2 POST4 PUT1 DELETE1
Inventory (Bin Level)
Read and maintain inventory balances records (scm.inventory_balances).
GET2 POST2 PUT1 DELETE1
Inventory Ledger
Read and maintain inventory transactions records (scm.inventory_transactions).
GET2 POST2 PUT1 DELETE1
Strategic Sourcing
Document Templates
The skeleton each kind of event is written from. A merge field the platform can answer is filled in; one it cannot stays visible as a placeholder.
GET2 POST2 PUT1 DELETE1
e-Auctions
A reverse auction only moves one way, and only by the declared decrement — the rule lives in the database, so no bid gets in by another door.
GET3 POST7 PUT2 DELETE2
Invitations
Every supplier asked to respond to a sourcing event, and whether they have. Invite more on the event itself, under Invited suppliers.
GET2 POST2 PUT1 DELETE1
Responses
What each supplier offered, and how it scored on the weights declared before the event opened.
GET3 POST3 PUT2 DELETE2
Sourcing Events
RFI, RFP and RFQ. Every response is scored and ranked as it arrives — on price, lead time, payment terms and any criteria the evaluators mark — and awarding against the ranking has to be said out loud.
GET9 POST15 PUT5 DELETE4
Supplier Management
Supplier Documents
What each supplier has on file and when it runs out. An expired certificate is a compliance failure waiting to happen.
GET2 POST2 PUT1 DELETE1
Supplier Onboarding
A supplier is not approved until the paperwork is on file. Submitting names everything still missing at once; approval creates the supplier record the rest of the platform buys from.
GET2 POST4 PUT2 DELETE1
Supplier Performance
Delivery and cost are measured from what actually happened; quality, service and compliance are judged. The overall score weights only what was scored.
GET2 POST2 PUT1 DELETE1
Supplier Risk
Likelihood times impact, with the mitigation and who owns it. The score and its severity are computed, not opinions.
GET2 POST2 PUT1 DELETE1
Supplier Portal
Supplier Change Requests
Contact, address and bank details suppliers asked to change from the portal. Nothing changes until it is approved here, and a new bank account arrives unverified.
GET2 POST4 PUT1 DELETE1
Supplier Portal Users
People at your suppliers and carriers who sign in to the supplier portal: invited by email, held to their own records, with a second step where you require one. People at customers are invited from CRM.
GET4 POST6 PUT1 DELETE1
Supply Planning
Material Requirements Planning
What a sales order needs, exploded through its bills of material and netted against stock and open supply. What is short is bought on a requisition naming the order, or made on a planned order that becomes its production order.
GET3 POST4
Planned Orders
What the run decided should be ordered, made or moved. A proposal until somebody firms it, and firming one produces a real requisition or works order.
GET2 POST5 PUT1 DELETE1
Planning Exceptions
What the run wants somebody to look at. A run that produced four thousand orders and no exceptions has told nobody anything.
GET2 POST2 PUT1 DELETE1
Projected Stock
What is on hand, what is coming, what is wanted, week by week for six months. The single most useful screen in planning and the one thing reorder advice could never show.
GET2 POST2 PUT1 DELETE1
Supply Plans
What would have to happen for the demand to be met. An INFINITE run assumes the factory can do whatever the plan asks; a FINITE one does not, and comparing them is exactly how a planner finds the bottleneck.
GET4 POST7 PUT3 DELETE3
Third-Party Logistics
Carrier Accounts
One set of credentials with one provider. Sealed the way every other connector in the product seals them, and never sent back to the browser.
GET2 POST3 PUT2 DELETE1
Logistics Providers
The integrations the platform knows how to speak, and what each one actually needs before it will work. "Configure your credentials" helps nobody.
GET2 POST2 PUT1 DELETE1
Shipping Labels
Labels that have been bought. Kept because voiding one is a real action with a real refund window, and reprinting is the commonest request a shipping desk gets.
GET2 POST2 PUT1 DELETE1
Traceability
Serial History
Read and maintain serial history records (scm.serial_events).
GET2 POST2 PUT1 DELETE1
Serial Numbers
Read and maintain serials records (scm.serial_numbers).
GET4 POST4 PUT1 DELETE1
Units & Packaging
Handling Units
The actual, physical, numbered thing on the floor: pallet, carton, container. They nest, and the weight of a parent is the sum of everything under it — maintained rather than typed, because a pallet whose weight is a guess is a pallet that overloads an axle.
GET4 POST5 PUT2 DELETE2
Item Units
Every unit one item may be transacted in, and what each is worth in the item’s stocking unit. This is what a purchase order line’s unit picker reads.
GET2 POST2 PUT1 DELETE1
Package Types
The pallets, cartons, totes, drums and containers goods are shipped in — with the outside dimensions and the tare weight that make a load plan arithmetic rather than an opinion.
GET2 POST2 PUT1 DELETE1
Packaging Materials
What goes into a pack and is not the goods: film, void fill, desiccant, the label. Costed, because packaging cost per order is a real number nobody can produce without it.
GET2 POST2 PUT1 DELETE1
Packing Instructions
How many go in the carton, how many cartons on the layer, how many layers on the pallet. One row per level, so a customer who wants it packed differently is a second instruction rather than an argument.
GET2 POST2 PUT1 DELETE1
Unit Conversions
The conversions arithmetic cannot derive. A rule with no item is a company rule; a rule with one belongs to that item and beats it.
GET2 POST2 PUT1 DELETE1
Units of Measure
A unit belongs to a dimension and carries a factor to that dimension’s base unit, so any two units of one dimension convert without anybody declaring anything.
GET2 POST2 PUT1 DELETE1
Warehouse Execution
Bin Utilization
How full each bin is against what it will take. The number the warehouse map colors by, and the one a putaway strategy checks before it proposes anything.
GET2 POST2 PUT1 DELETE1
Labor Performance
What one person actually did in one shift, against the standard. The row that makes warehouse productivity reportable next to the roster and the payroll.
GET2 POST2 PUT1 DELETE1
Labor Standards
How long one of these tasks ought to take. Split into fixed and variable, because walking to the bin costs the same whether you pick one case or ten.
GET2 POST2 PUT1 DELETE1
Slotting
Where each item OUGHT to live, given how it actually moves. A recommendation with its reasoning attached, so nothing is moved without somebody agreeing to it.
GET3 POST3 PUT2 DELETE2
Warehouse Orders
A bundle of tasks for one person to do in one go. The unit of assignment, as opposed to the unit of work.
GET3 POST3 PUT2 DELETE2
Warehouse Tasks
One move: this quantity of this item, from this bin, to that one. Every kind of warehouse work is this shape, which is why there is one list rather than six. Confirming a task is the only thing here that moves stock.
GET2 POST3 PUT1 DELETE1
Waves
The decision to work on THESE orders now. Picking one order at a time walks the same aisle forty times; a truck leaving at four means the work starts at one.
GET3 POST4 PUT2 DELETE2
What Needs Replenishing
Every pick face at or below its minimum, right now. The replenishment run reads exactly this and turns each row into a task.
GET2 POST2 PUT1 DELETE1
Warehouse Structure
Dock Doors
Where a vehicle meets the building. A real constraint: two trailers cannot be on one door, and a load whose door is occupied is a load that will not leave on time.
GET2 POST2 PUT1 DELETE1
Putaway Rules
Which storage type an arriving item should go to, in what order to try. Evaluated most specific first: a rule naming this item beats one naming its category.
GET2 POST2 PUT1 DELETE1
Replenishment Rules
Keeping the pick face full from the reserve, so a picker never walks to an empty bin.
GET2 POST2 PUT1 DELETE1
Staging Areas
Where goods wait between the door and the rack, or between the pick and the truck. Measured in pallet positions and floor area, which is why it is not a bin.
GET2 POST2 PUT1 DELETE1
Storage Types
What KIND of space each area is, and the two decisions that follow from it: how stock is put away there and how it is taken out.
GET2 POST2 PUT1 DELETE1
Warehouse Resources
The people, trucks and handhelds that do the work. A resource that is a person IS an employee, so their productivity is reported against their record and a leaver stops being a resource without anybody remembering to do it here.
GET3 POST2 PUT1 DELETE1
Warehouse Systems
Warehouse Messages
Every message exchanged with another system, what it mapped to and what became of it. Append-only.
GET2 POST2 PUT1 DELETE1
WMS Connections
Another system already runs the warehouse. Map its field names to these and its movements arrive as scan sessions — no code changes to take another one on.
GET3 POST5 PUT2 DELETE2
Yard
Yard Locations
The spots a trailer can stand in, and which of them are on a door.
GET2 POST2 PUT1 DELETE1
Yard Movements
A trailer stay: it arrived, it sat here, it went on a door, it left. Dwell time is what this exists to produce, because detention is charged by the hour and nobody can argue about it without a record. Booking a truck’s arrival at a gate or door against an order is a Dock Appointment, not a yard movement (IN PFC TKT-000009).
GET2 POST2 PUT1 DELETE1