The platform is built and maintained in house. A change Pilot needs is something we decide, not something we request.
Our ordering platform supports high volumes of traffic and transactions simultaneously. The cloud-hosted environment scales elastically with demand, which is what keeps performance steady through the events that actually stress a company store — a program launch, a seasonal spike, a company-wide initiative.
We employ internal technical resources, including a dedicated software engineering team, supporting integration, reporting, platform development and evolving customer requirements.
| Requirement | What it does | Status |
|---|---|---|
| Per-user accounts | Magic link, one-time code or password, held to Pilot's email domains | Operational |
| Role-based access | Shopper, user, regional admin, store admin, organization admin | Operational |
| Manager hierarchy | Each person's approver, held on the record and used for routing | Operational |
| Bulk employee import | People, roles and managers loaded from a file | Operational |
| Role-based catalogs | Which pages and which products a role may see | Operational |
| Access codes | A catalog behind a code that is never published to the browser | Operational |
| Order approval | Every order, or only the ones a policy catches | Operational |
| Approval policy | Over an amount, a named payment method, a named buyer, or any custom build | Operational |
| Approval by email | A one-time link, so an approver who never signs in lands in the same record | Operational |
| Allowances and budgets | Credit granted per person, reserved at checkout, released if the order is refused | Operational |
| Payroll deduction | Checkout with no card; the organization is billed and deducts from pay | Operational |
| Purchase orders | PO number captured at checkout, carried through to the invoice | Operational |
| Company-paid ordering | The employee sees $0; the real price sits against the organization | Operational |
| Card payment | Authorized at checkout, captured on approval, card data never held by us | Operational |
| Payment method access | Which people may pick which method | Operational |
| Cost center capture | Custom fields answered per order, or held once against the person | Operational |
| Ship-to address book | Corporate addresses, scoped by who may use them | Operational |
| Live inventory | Stock read from the ERP, with a restock estimate rather than a hidden size | Operational |
| Order tracking | Carrier and number per line, pushed as each transfer is validated | Operational |
| Partial shipments | Each line carries its own fulfillment state | Operational |
| Decoration library | Approved logos held against the store, not retyped per order | Operational |
| Personalization | Names, numbers and custom text captured on the line | Operational |
| Promotions | Codes with their own redemption limits | Operational |
| Reporting | Store totals, the same money by item and by buyer, and an inventory position | Operational |
| Exports | Excel and PDF, from the page showing the figures | Operational |
| Support impersonation | An administrator can act as a buyer to reproduce a problem | Operational |
| Audit log | Every administrative change, with the person who made it | Operational |
| Multi-store, one login | One account spanning every Pilot store, present and future | Operational |
| ERP integration | Signed publishes and order pushes, retried until they land | Operational |
Integration
- API integrations.
- EDI integrations.
- Support for EPS integrations.
- Support for Pilot-required integrations.
- Secure ordering environments.
- Administrative user controls and approval workflows.
We support both API and EDI connections to exchange order, inventory, shipping and invoicing information, and can support the integrations Pilot requires.
Integrate Pilot's HR management systems directly with Storefront and a new employee is onboarded the moment they are entered there — with their permissions and their user attributes already set, so their first sign-in shows the right catalog and charges the right budget.
Automated email at order confirmation, at shipment, and with tracking. An employee should not have to ask where an order is.
We update and implement new technology continuously rather than holding a platform still between contracts. The engineering is in house, so an improvement is a decision we make.
Security
We build on infrastructure that is independently audited, so Pilot's security review does not come down to taking our word for it.
The providers hosting this platform and its data hold SOC 2 Type II attestations and ISO 27001 certification, renewed annually by third-party auditors, and run GDPR and CCPA compliance programs. Their audit reports are available to Pilot under NDA on request.
- Encryption in transit and at rest, as the default rather than a setting.
- Isolation enforced in the database itself. Every row carries the store it belongs to, and a query that does not match returns nothing — not fewer rows, none. One store cannot read another's orders, and neither can anyone without a server-side credential.
- Card data never reaches our systems. Payment runs through a PCI DSS Level 1 gateway; we hold a token, not a number.
- Credentials never reach our ERP. Registration, sessions and password policy sit with an audited identity provider, which takes both out of our audit scope.
- Signed, time-limited requests between the store and the ERP, with a replay window measured in minutes.
- Administrative actions are logged against the person who took them.
- DDoS mitigation and a managed web application firewall at the edge.
- Point-in-time database recovery, so a bad hour is recoverable rather than a bad day.
Security questionnaires, the providers' current audit reports, penetration test summaries and a data flow diagram for the Pilot program. We would rather answer these during evaluation than at implementation.