How CaterAxis connects to the systems around the catering order
Current capabilities are separated from provider-specific connector work.
CaterAxis can receive or upload ezCater™ order documents, identify the source, analyze the attachment, preserve the original file and turn the extracted information into a CaterAxis order workflow.
CaterAxis is designed to sit alongside an existing POS instead of forcing a restaurant to replace it. A provider-specific connector can map products, sizes, modifiers, customers and status data according to what that POS API supports.
What “rendering into CaterAxis” means
POS / ezCater™ / email / upload / manual
Customer, date/time, fulfillment, products and modifiers
Translate outside item names to the CaterAxis menu
Show the same order on Order Entry, Dashboard and Kitchen
Archive the order, customer history, PDFs and original source files
Email Receiving
Inbound attachments can be routed by location, stored, analyzed and presented for import review.
Cloud File Storage
Original order documents can be retained in DigitalOcean Spaces and linked back to the operational order.
Stripe Billing
Company subscriptions use Stripe-hosted checkout/customer portal flows and webhook synchronization.
Important POS / ezCater™ distinction
CaterAxis should not advertise a live direct POS or direct ezCater™ account API connection until the corresponding provider credentials and connector are implemented. Today, ezCater™ order intake can already work through the email/document import path. POS integration is architecture-ready but provider-specific connector work is still required.