OrderTime Automation
OrderTime to OnPart Inventory Feed Automation
Partner inventory-feed automation that turns OrderTime API inventory records into a mapped, validated, audit-ready CSV feed delivered through controlled FTP / FTPS publishing.
Inventory feed command view
OrderTime to OnPart Feed Automation
API extraction, 26-column mapping, audit manifests, and atomic FTP delivery
Extract
OrderTime API
Map
26 columns
Validate
Rules
Package
CSV + JSON
Deliver
FTP / FTPS
Feed controls
Feed preview
CSV delivery| Part | On Hand | Type | Status | Output |
|---|---|---|---|---|
| 100-4412 | 12 | CAPA | Eligible | Publish |
| 225-0198 | 0 | OEM | Filtered | Skip |
| 300-7710 | 8 | AM | Eligible | Publish |
| 410-2250 | 3 | OD | Review | Audit |
Delivery flow
Business problem
Partner inventory feeds needed repeatable mapping, business rules, quality checks, and controlled delivery. Manual feed preparation created risk around incomplete data, inconsistent formatting, and unreliable publishing.
The process needed an automated way to pull inventory from OrderTime, shape it to the partner schema, verify the output, and publish the file safely.
System built
Built a feed generator with OrderTime API extraction, 26-column partner mapping, on-hand filtering, OD / AM / CAPA business-rule handling, audit CSVs, JSON manifests, health checks, drift monitoring, and FTP / FTPS upload.
The system turns inventory data into a partner-ready feed with supporting evidence, delivery controls, and safer atomic upload behavior.
Feed signals
Signals reviewed
The feed pipeline evaluates inventory availability, schema mapping, business rules, output readiness, and delivery status before publishing downstream.
Feed generation flow
How it works
Extract
Pull inventory records from OrderTime API sources and prepare source data for partner-feed generation.
The workflow starts by retrieving the inventory data needed to build the outbound feed instead of manually preparing files.
Map
Transform source records into the required 26-column partner inventory-feed schema.
The mapping layer standardizes fields, aligns output names, and shapes the data for partner-side consumption.
Validate
Apply on-hand filtering, business rules, eligibility checks, and output readiness checks before delivery.
The validation layer helps prevent bad, empty, or malformed feed files from being published downstream.
Package
Generate the partner-ready CSV along with audit files and JSON manifests that describe the run.
This creates both the business output and the supporting evidence needed to troubleshoot, review, or monitor the feed.
Deliver
Upload the feed using controlled FTP / FTPS delivery with atomic .part then rename behavior.
The delivery layer reduces the chance of a partner reading a partially uploaded file and makes publishing safer.
Automation layers
What the feed system coordinates
API extraction
Connects to OrderTime inventory data and pulls the source records required for the outbound partner feed.
Feed mapping
Converts inventory records into the required 26-column schema expected by the receiving platform.
Quality checks
Applies on-hand filters, business rules, audit checks, and output validation before delivery.
Controlled upload
Publishes the feed through FTP / FTPS using atomic upload behavior and run manifests.
Impact signals
What the automation improved
Partner-ready inventory feed from OrderTime API data
26-column mapping into a controlled outbound schema
Atomic .part then rename upload for safer delivery
Audit CSVs and JSON manifests for run traceability
Health checks and drift monitoring for ongoing feed reliability
Operational value
Partner feed delivery with stronger controls
Less manual feed work
Replaces manual inventory-feed preparation with repeatable API extraction, mapping, validation, and delivery.
Cleaner partner output
Shapes inventory records into a consistent partner-ready CSV rather than relying on ad hoc exports.
Safer publishing
Atomic upload behavior helps prevent incomplete files from being consumed by the partner system.
Better supportability
Audit files, manifests, and health checks make the feed easier to monitor, troubleshoot, and explain.
Why this project matters
An inventory feed turned into a controlled delivery pipeline.
This project shows how a partner feed can be treated like an operational system instead of a file export. API extraction, mapping, validation, audit outputs, manifests, and atomic upload behavior work together to make delivery more reliable.
The value is not just creating a CSV. The value is building a repeatable feed pipeline with controls that help protect downstream partner workflows.
Confidentiality note
Visuals and descriptions are sanitized conceptual representations. They do not expose private company data, customer records, credentials, raw exports, internal pricing, operational screenshots, FTP destinations, or proprietary source files.