Client account sign-in
Each client's procurement and facilities staff see only their own program, invoices and documents.
A customer portal website for corporate caterers gives facilities teams, executive assistants and procurement staff a login for recurring orders, invoices and vendor documents. SIZ Group builds that portal so each client's paperwork lives in one place instead of across a dozen email threads.
A facilities manager with a weekly lunch program does not search every week. They judge the caterer on invoice clarity, reorder ease and vendor onboarding when the contract renews, and they ask colleagues about on-time delivery. A recurring client weighs the admin work as heavily as the food.
The portal should make renewals simple: current terms, the price sheet by event type, vendor documents already on file and an easy way to repeat an order. A client who finds those things in one place stops asking for them by email.
Sales conversations rarely start with price alone. Buyers want to know that the paperwork will be easy to handle the day their finance team asks for it, and a portal that holds those records answers that question before it is asked.
The first version should cover sign-in for each client account, reordering a standing program, invoice history with purchase order numbers and a document area for insurance certificates and vendor forms. Those four areas handle most recurring requests. Every addition would need its own testing, so the first version stays focused on repeat orders and documents.
Live headcount sync with the kitchen, a client budget dashboard and multi-currency invoices can wait. They suit larger accounts, but each one adds rules to test before the core flow is trusted.
Many corporate caterers keep event records in Tripleseat or Caterease, bill through QuickBooks and store contracts in Google Drive or in DocuSign envelopes. The portal should read from those records where it can, rather than force a second copy of every event.
Invoices can carry the purchase order number from the client account, and the export should match what the bookkeeper imports. Document requests can point to the file in existing storage, so the client always sees the latest certificate. Where the accounting package holds customer records, the portal can read the same name and address, which avoids two versions of a client.
Each client's procurement and facilities staff see only their own program, invoices and documents.
Repeat last month's recurring order, adjust the headcount and confirm the delivery window.
Past invoices carry purchase order numbers and can be exported for accounts payable.
Insurance certificates and vendor forms sit in one place, with expiry reminders for the team.
Before a build starts we need the client list with account owners, the price sheet by event type, the current vendor documents including the certificate of insurance and W-9 form, and the invoice format each client's accounts payable team requires.
Access rules need writing down too: which staff can see which accounts, who approves a new client and who can edit a standing order. Settling those answers early avoids a rebuild later. Each client's contract terms, such as payment windows or a required insurance limit, should be listed in the same place as the price sheet.
A portal serving several client accounts with invoices and documents lands toward the upper end of a $300 to $2,200 band. Client tiers, custom pricing per client, the depth of the accounting connection and the number of document types all move the figure. Ask for a written list of every document type before the build, so the cost of each one is clear.
A portal for a handful of clients costs far less than one serving dozens of accounts with unique terms. We keep the first release narrow and quote later phases separately, so the boundary is clear before anything is built. A client with a dozen recurring events a year should see a price for each event type without calling anyone for a quote.
Clients adopt a portal when their procurement contacts receive a personal invitation and the first login shows their own documents and invoices. We would send invitations in batches so the office team can answer questions as they arrive.
The office team needs a simple routine: approve new accounts, update the price sheet when it changes and check that documents are current every month. A short handover with the owner covers all three.
Figures run from $300 to $2,200, and a portal serving several client accounts with invoices and documents lands toward the upper end. Client-specific pricing, accounting links and the number of document types set the figure. A written proposal confirms it.
No. Each account has its own permissions, and document and invoice lists show only files tied to the signed-in account. Staff access is logged, and we test the rules with two accounts before sign-off.
If Tripleseat, Caterease or your current event system offers an export or connection, we use it to avoid double entry. Where it does not, we agree a manual step and record who owns it. We confirm your setup during the first call. The connection is set up once and tested with a sample event before the first live client logs in.
The portal stores an expiry date for each document and reminds the team and the client ahead of that date. Expired documents are flagged on the admin screen, so no account is quietly out of compliance.
Yes. New accounts are created from an admin screen and receive an invitation only after an approver signs off. You decide who can approve, and every approval is logged.
Describe your recurring accounts on a call, and we will put the scope in writing before any work starts.