Frequently asked questions

CaterDeck is a B2B lunch coordination and marketplace platform for companies. Companies match with caterers; menu publishing, employee selection, headcount, deadlines, delivery coordination, feedback, invoice reconciliation, and collection tracking run through CaterDeck. Food production, packaging, and delivery are performed by the relevant caterer.

There are two phases. In discovery, the company reviews caterers in the marketplace and sends a match request. No sale, invoice, or payment happens at this stage. In active service, the company's platform terms, the caterer's intermediation agreement, and the active link/transaction record for each match work together. The active link binds price, location, delivery time, deadline, invoice, and collection terms.

No. CaterDeck does not produce, package, or deliver meals. CaterDeck provides the intermediation platform, operational coordination, and collection/reconciliation infrastructure. The relevant caterer is responsible for production, packaging, labeling, allergen information, hygiene, and delivery.

Caterers manage menus, prices, delivery times, and capacity. Company admins track employees, selections, headcount, delivery status, and monthly reconciliation. Employees choose lunch, change selections, skip days, and rate the meals they receive.

Yes. Your current caterer can join CaterDeck and remain your meal-service provider. Before active service starts, the caterer goes through onboarding; food-business registration or approval, workplace license, tax certificate, signing authority, capacity, and other required documents are checked. Daily selections, headcount, delivery tracking, invoice reconciliation, and collection then run through CaterDeck.

Yes, it is an alternative workplace-lunch line to meal cards. No card, wallet, balance, or payment instrument is issued to employees. Lunch comes to the workplace, and employees only make selections in the app. For the company, daily headcount gathering, WhatsApp/Excel chasing, restaurant calls, and invoice reconciliation move into one platform flow. Payroll, SGK, and tax effects should be confirmed with the company's own accountant.

In most companies, lunch coordination means daily headcount chasing, WhatsApp/Excel tracking, delivery checks, and invoice reconciliation. With CaterDeck, employee selections are captured in the platform; headcount, menu, deadlines, delivery, and monthly reconciliation are visible in one panel. The admin works on exceptions, approvals, and service quality rather than daily chasing.

Under the intermediation model, the food-service invoice is issued by the relevant caterer to the company. CaterDeck does not resell the meal service or issue the food invoice to the company. Under the platform terms and the caterer's collection authorization, CaterDeck may collect payment from the company; that payment settles the company's debt to the relevant caterer. CaterDeck earns its revenue through the intermediation/service-fee invoice it issues to the caterer. The target company experience is one reconciliation and payment flow.

In the pilot model, after month close the company pays by bank transfer to the collection account designated by CaterDeck. Under the contractual collection authorization, this payment is treated as payment to the relevant caterer. CaterDeck matches the collection, applies any credits/adjustments and service-fee offsets, and pays the caterer's net entitlement on the agreed schedule.

Before the deadline, employee selections and bulk orders can be updated. After the deadline, changes affect production and may not be accepted automatically in the platform; CaterDeck and the caterer may need to confirm them manually.

Yes. The company accepts the platform terms once, and the caterer operates under CaterDeck's intermediation agreement. Each new match is opened through an active link/transaction record. This lets the company switch caterers inside the platform; a separate wet-signed company-caterer agreement is not the target flow for each switch.

In the target flow, no. The company accepts CaterDeck's platform terms; the caterer accepts CaterDeck's intermediation agreement; the standard food-service terms between the company and the caterer are bound through the active link/transaction record. The active link records the caterer, service period, location, price, delivery time, deadline, invoice, and collection terms.

The pilot target is no fixed term and no minimum commitment on the company side. The company can end an active match through the platform or by written notice. Days whose deadline has not passed are cancelled; days past the deadline may be delivered and included in invoice reconciliation because production has started. Past invoice, collection, and dispute records are retained for the legally required periods.

Employees rate the meals they receive. The company sees satisfaction trends, and CaterDeck uses feedback for quality and SLA tracking. Feedback is not shared with the caterer under the employee's name; the caterer sees anonymized summaries and the quality issues that need action.

CaterDeck is the first operational point of contact. Late delivery, missing portions, quality complaints, allergen claims, and food-safety incidents are reported to CaterDeck. CaterDeck follows up with the caterer and, where needed, runs the credit, adjustment, substitution, or entitlement-offset process under the contractual rules.

Yes. Employees can choose meals for upcoming days, change their selections, or skip days when they will not be on-site. Company admins can also add bulk needs separately.

CaterDeck's marketplace helps companies find you and send match requests. If a request turns into active service, an active link/transaction record opens under the intermediation agreement; menu, price, location, delivery time, and collection terms are bound through that record. This does not guarantee demand, but it creates a professional sales and operations flow with new companies.

No. You publish the menu, price, delivery time, capacity, and selection deadline in the platform. In the kitchen, the change is that production starts from confirmed headcount after the deadline instead of guesswork. Packaging and delivery remain your operation.

Yes. Employee selections and bulk orders close before the deadline, so you plan capacity from confirmed headcount rather than a forecast. Starting production from a fixed portion count reduces waste and last-minute operational stress.

The pilot commercial model is service-fee based. Setup or fixed monthly fees are not the target. The service-fee rate and any offset rules are written in the intermediation agreement and active link/transaction record. After the company's payment reaches the CaterDeck collection account, CaterDeck offsets the service fee and any credits/adjustments, then pays your net entitlement on the agreed schedule.

Yes. You can redeem a company's invite code to open a partnership request, or accept requests that arrive through the marketplace. Once the match turns into active service, your food-service relationship with the customer runs through the active link/transaction record; CaterDeck provides coordination, selection, headcount, collection, and reconciliation infrastructure.

Yes. Menu assignments, headcounts, deliveries, invoice amounts, collection status, and entitlement summaries are tracked separately for each company. In the kitchen, you see total production needs in one place.

You are the food-service provider; CaterDeck manages the platform, marketplace, coordination, collection, and reconciliation layer. Direct off-platform work with companies introduced or managed through CaterDeck is subject to the non-circumvention and off-platform transaction rules in the intermediation agreement.

Yes. You set which menu opens for which company, the delivery time, the selection deadline, and operational capacity limits. CaterDeck binds this information to the platform rules and the active link/transaction record.

In the target flow, no. The CaterDeck intermediation agreement is accepted once; later company matches open as active links/transaction records. A new wet-signature round is not the target for every customer, but price, menu, delivery time, location, invoice, and collection terms are recorded separately for each match.

The intermediation agreement covers termination, notice period, ongoing menu assignments, and entitlement reconciliation. Active links are transitioned so companies are not left without lunch. CaterDeck reserves the right to suspend or terminate assignments for quality, food-safety, document-compliance, data-use, or off-platform transaction breaches.

The intermediation agreement includes non-circumvention and off-platform transaction rules. Companies introduced through or managed on CaterDeck cannot be served by bypassing CaterDeck during the period and scope written in the agreement. This protects CaterDeck's marketplace and coordination work.

Before active service starts, CaterDeck checks food-business registration or approval, workplace license, tax certificate, signing authority, capacity declaration, the person responsible for menu/allergen disclosures, and any insurance or extra certificates deemed necessary. The document scope can vary by risk level and service model. New menu assignments may be suspended if a document is expired or materially non-compliant.

No, it is not required. Employees can install the CaterDeck app from the app store or use it directly on the web. Additional channels such as Slack, Microsoft Teams, and WhatsApp may be considered later.

Yes. Before the deadline, an employee can select, change, or skip the meal for that day. If no selection is made, that day may be treated as a skip.

Instead of spending lunch on commuting, queues, parking, and waiting, the employee finds a hot meal at the workplace. The employee does not pay out of pocket and does not have to track a meal-card balance or settle a bill at a restaurant. If a meal disappoints, they rate it; the feedback is used for quality tracking without naming the employee to the caterer.

No. CaterDeck does not issue any meal card, wallet, balance, coupon, or payment instrument to employees. The app is used only to choose a meal and consume the workplace service; employees do not pay at a restaurant or off-site.

In the pilot model, a separate setup or fixed monthly fee for the company is not the target. The company pays the relevant caterer invoice to the collection account designated by CaterDeck; under the contractual collection authorization, that payment settles the company's debt to the caterer. CaterDeck's revenue comes from the intermediation/service-fee invoice issued to the caterer.

Yes, under the pilot intermediation model collection runs through CaterDeck. This is not an employee wallet, payment account, escrow, or payment-services product. The caterer authorizes CaterDeck to collect receivables created through the platform; when the company pays CaterDeck, it settles its payment obligation to the relevant caterer. This model is subject to lawyer and accountant confirmation.

The pilot target is that the company pays into the CaterDeck collection account no later than the 7th day after month close. If collection and invoice/headcount reconciliation are complete, CaterDeck pays the caterer's net entitlement no later than the 14th day after month close. If the company payment is late, the caterer is not given an unconditional payment guarantee; delay notices and suspension of new menu assignments may apply.

No. CaterDeck does not provide tax, payroll, or SGK advice. Under the intermediation model, the food-service provider is the caterer; the caterer issues the food-service invoice to the company. CaterDeck issues an intermediation/service-fee invoice to the caterer. KDV, withholding, payroll, and SGK outcomes must be confirmed with the company's and the caterer's own accountants.

CaterDeck is a product operated by POIEX TEKNOLOJİ LİMİTED ŞİRKETİ. Platform terms, the caterer intermediation agreement, collection/reconciliation infrastructure, and KVKK data controllership run through POIEX. The food-service invoice is issued to the company by the relevant caterer.

CaterDeck processes the data needed to run the service, such as account, role, organization, meal selection, delivery, billing period, collection reference, support messages, feedback, menu-level allergen/ingredient information, language, and cookie preferences. At pilot launch, CaterDeck does not collect person-level allergy, diet, or health-sensitivity profiles. If such a feature is introduced later, it will require separate explicit consent and withdrawal flows.

By default, no. The caterer sees only the minimum operational data needed for production and delivery: menu counts, location, delivery time, total headcount, and anonymized quality summaries. The employee's name, phone, person-level selection, person-level allergy/diet information, and person-level comment are not shared with the caterer. KVKK roles are documented separately in the contractual data-sharing addendum.

Menu content, allergen disclosures, labeling, production hygiene, and food-safety practices are the caterer's responsibility. CaterDeck provides the platform and coordination infrastructure for document checks, menu disclosures, complaints, and incident tracking. Employees with serious allergies or special health conditions should check menu ingredient information and, where needed, confirm separately with their company contact or the caterer.

To start a pilot, the company must accept the platform terms, the caterer must complete the intermediation agreement and onboarding checks, the active link/transaction record must be opened, menus must be published, and deadlines/delivery times must be set. Once these are in place, employee selections open and the first delivery is scheduled.

A company can send a request to a caterer from the marketplace, or a caterer can use the company's invite code to open a partnership request. When the match is approved, an active link/transaction record is created; menu, price, location, delivery time, deadline, invoice, and collection terms run through that record.