Frequently asked questions

iştebu! brings the daily meal process for companies and schools together with their caterers in one platform. Caterers publish menus; employees choose their own meals and guardians choose for their children. The institution tracks meal counts, delivery, feedback, and billing. The caterer remains responsible for production, packaging, and delivery.

An institution starts working with a caterer. The caterer sets menus and selection deadlines, then employees or guardians make their choices. When selection closes, the confirmed meal count goes to the kitchen. The institution tracks delivery, feedback, and billing from its dashboard.

No. iştebu! does not produce or deliver meals. It brings selection, ordering, delivery tracking, feedback, and payment workflows together. The caterer providing the service is responsible for production, packaging, labeling, allergen information, hygiene, and delivery.

Caterers manage menus, confirmed meal counts, and delivery. Company and school administrators track choices, meal counts, delivery, and billing. Employees choose their own meals, while guardians choose for their children; delivered meals can then be rated.

Yes. Your current caterer can join iştebu! and continue serving your company. At onboarding, it uploads its tax certificate and Food Business Registration Certificate; the authorized review team compares the entered details with those documents. Daily selections, meal counts, delivery tracking, invoice reconciliation, and collection then run through iştebu!

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 iştebu!, 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. iştebu! does not resell the meal service or issue the food invoice to the company. Under the platform terms and the caterer's collection authorization, iştebu! may collect payment from the company; that payment settles the company's debt to the relevant caterer. iştebu! earns its revenue through the intermediation/service-fee invoice it issues to the caterer. The company sees one reconciliation and payment process.

The company pays the caterer's invoice by bank transfer to the collection account designated by iştebu! Under the contractual collection authorization, this payment settles the company's debt to the caterer. iştebu! matches the collection to the invoice and service period, deducts the service fee and any adjustments, and pays the caterer's net entitlement on the contractual 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; iştebu! and the caterer may need to confirm them manually.

Yes. The company accepts the platform terms once, and each caterer operates under an intermediation agreement for the iştebu! platform. A new match opens as an active service record. Switching caterers does not require a new wet-signature process with iştebu!; the terms of the new service are recorded separately in the platform.

No. The company accepts the iştebu! platform terms, while the caterer accepts the platform's intermediation agreement. For each match, the caterer, service period, delivery address, price, delivery time, selection deadline, invoice, and collection terms are attached to an active service record.

The agreement has no fixed term. The company may terminate it with 30 days' written notice; that notice period does not apply to termination for cause. Days whose selection deadline has not passed are cancelled. Days past the deadline may still 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 eat and may add a note. The company sees only overall satisfaction trends. The optional note reaches the caterer together with the rating and tags, but is not linked to the employee's account or meal selection. If the person identifies themselves in free text, the caterer may see that information. iştebu! uses feedback for quality and SLA monitoring.

iştebu! is your first point of contact. Report late delivery, missing portions, quality complaints, allergen claims, and food-safety incidents to iştebu!. We follow up with the caterer and, when needed, handle credits, adjustments, substitutions, or entitlement offsets under the contract terms.

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.

A guardian chooses from the menu available for each child. They see the food description, allergens, dietary and special-content labels, and calorie information published with the menu, then can change the choice until selection closes. The school tracks completed and missing choices in the same system.

Yes. Guardians see the published menus, meal photos, and food information, choose for their child, and share feedback afterward. Families therefore know what will be served and can take part in the school meal experience.

Yes. Your current caterer can join iştebu! and continue serving the school. We set up the shared flow with the school and caterer so menus, choices, confirmed counts, feedback, and billing stay together.

Yes. The selection screen shows the food description together with allergen, dietary, special-content, and calorie information added to the menu. This information is not medical advice; families managing a serious allergy or health condition should also confirm directly with the school and caterer.

The school tracks published menus and each child's choices in the same system. Confirmed meal counts go to the caterer, while administrators see costs, invoices, and feedback trends in one place.

Companies and schools can review your business in the iştebu! marketplace and send a match request. If a request becomes active service, the menu, price, delivery plan, and payment terms are recorded. The marketplace does not guarantee demand or revenue.

Production, packing, and delivery remain your operation. The change is that menus and customer orders come together in one place. Once selection closes, you see confirmed order counts by dish and plan preparation from those counts.

While selection is open, the demand forecast helps you plan early preparation. Once selection closes, the estimate gives way to the confirmed order count; completing production from confirmed orders may help reduce waste. The result depends on your menu, operation, and order variability.

The service fee, payment schedule, and any adjustments are confirmed in writing before service begins. After the customer organization’s payment reaches the iştebu! collection account, the service fee and any adjustments are deducted and your net entitlement is paid on the contractual schedule.

Yes. Use the invite code of a company or school you already serve, or accept a request from the marketplace. Once service begins, menus, selections, confirmed counts, delivery plans, invoices, and payouts run through the same system.

Yes. Menus, meal counts, delivery plans, invoice amounts, collection status, and payout summaries are tracked separately for every company or school. The kitchen view brings total preparation needs together.

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

Yes. In the service plan, you set which menu opens for each customer, the delivery time, and the selection deadline. Both sides can see this information.

No. The iştebu! intermediation agreement is accepted once. Each later customer match opens as an active service record; price, menu, delivery address and time, invoice, and collection terms are recorded separately for every service.

Either party may terminate with 30 days' written notice; no notice period applies for cause, such as a critical food incident, document cancellation, or rule breach. Termination does not extinguish accrued payout and collection obligations; future menu assignments for the caterer–customer pair are cancelled.

The intermediation agreement includes non-circumvention and off-platform transaction rules. Customer organizations introduced through or managed on iştebu! cannot be served by bypassing iştebu! during the period and scope written in the agreement. This protects the marketplace and coordination work of the iştebu! platform.

At onboarding, you upload the tax certificate and Food Business Registration Certificate. The authorized review team compares the tax and food-business registration details entered in the system with those documents. The documents are not shared with customers.

No, it is not required. Employees can install the iştebu! 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, no meal is prepared for that employee that day.

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. iştebu! 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.

The company does not receive a separate service invoice from iştebu! The caterer invoices the company for the meal service, and the iştebu! service fee is included in the quoted per-person total. The company pays the collection account designated by iştebu!, while iştebu! issues its own service-fee invoice to the caterer.

Yes. Collection runs through the account designated by iştebu! This is not an employee wallet, payment account, escrow account, or payment-services product. The caterer authorizes iştebu! to collect receivables created through the platform; when the company pays that account, it settles its payment obligation to the relevant caterer.

The caterer may combine one or more completed weekly reconciliation records into a single invoice. The company pays within 5 days of the invoice date. Once collection arrives and reconciliation is complete, the caterer's net entitlement is paid within 5 days. If company payment is late, there is no unconditional payment guarantee.

No. iştebu! 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. iştebu! 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.

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

iştebu! 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. iştebu! does not currently 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.

Only the information needed for production and delivery is shared: total meal and menu counts, delivery address and time, and first and last name for delivery labels. Phone and email address and person-level allergy or diet profiles are not shared with the caterer. The rating, tags, and optional review note are shared with the caterer; the employee's account and selection records are not linked to them. Free text may contain identifying details the person chose to write. 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. iştebu! 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.

The company must accept the platform terms, the caterer must complete the intermediation agreement and initial checks, the active service record must be opened, menus must be published, and selection and 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.