Robotic Cosmetics Retail Island with AI Virtual Try-On

Short answer: a double-sided robotic cosmetics retail island can combine eight brand bays, two simultaneous customer journeys, AI virtual try-on mirrors, multilingual touchscreens, unattended payments, and a department-store API. It should not be quoted as eight displays bolted onto a vending cabinet. It is a coordinated retail system, and the first quotation needs to define who supplies, integrates, licenses, tests, and supports every layer.

This distinction changes the project. Two robots can increase throughput, but only if their work envelopes and orders remain independent. Eight virtual mirrors can create a strong beauty experience, but they also create eight cameras, eight display endpoints, catalog-mapping work, privacy decisions, and perhaps eight license obligations. Arabic, English, and French can share one interface, yet right-to-left behavior must reach much further than the home screen. A card reader can fit into the cabinet before anyone confirms that the intended Lebanese acquirer supports it, but that is exactly how expensive redesigns begin.

The practical goal is a pilot that arrives as one tested unit rather than a collection of subsystems that meet for the first time on a department-store floor. This guide explains the architecture, quotation structure, acceptance evidence, and commercial boundaries a buyer should settle before detailed drawings are frozen.

Prepared by Adolf, Sales Engineer at OBO Tech Group. The guide is based on recurring custom-vending RFQ questions, OBO machine and control-system planning, and public documentation for virtual try-on, bidirectional interfaces, payments, trade terms, and product compliance. Final specifications require real product samples, site data, local payment confirmation, and engineering review.

Image note: this is an original OBO concept visualization produced to explain a double-sided robotic beauty island. It is not a photograph of a delivered customer project, not a final industrial drawing, and not a promise that every visible feature is included in a standard model.

This Is a Retail Island, Not a Larger Cosmetics Vending Machine

A conventional cosmetics vending machine has one customer face, one payment point, one controller, and a compact product-selection area. A retail island changes the spatial and operational logic. People approach from both directions. Four brands may occupy each side. Store staff need access without blocking both customer paths. The display has to look like permanent department-store furniture while still opening like serviceable industrial equipment.

That creates a mixed design problem: retail architecture outside, automation inside. Brand bays need visual separation, controlled lighting, replaceable graphics, product testers or digital content, and enough flexibility for seasonal launches. Behind them, the machine needs rigid robot references, secured inventory, cable routing, ventilation, emergency access, fire-conscious material choices, and doors large enough to replace a robot or screen later.

The existing cosmetics vending machine project planning guide covers the foundation. The system here is one level more complex because customer experience, merchandising, robotic handling, AI software, payments, and store integration must all agree on the same product and order.

Start With the Customer Journey Before Choosing the Robot

A useful design session begins with a shopper, not a mechanism. Does the customer browse one brand bay, use that bay’s mirror, then add one or several products to a basket? Can a shopper move from a lipstick try-on at one bay to fragrance at another? Does the touchscreen on the end control all four bays on that side, or does each bay have its own interface? What happens when one person is still comparing shades and another wants to pay?

A clean journey might be: choose language, browse or scan a brand bay, try a supported shade, select the exact sellable SKU, confirm basket and stock, pay on the same side, watch the robot retrieve the item, and collect it from that side’s pickup port. The transaction then posts to the island dashboard and the store’s POS or inventory system.

That sounds obvious. The difficult details are hidden inside it. A try-on shade must map to a real SKU and current stock. The mirror cannot recommend a product that the robot cannot reach. The second customer must not receive the first customer’s item. A payment approval should not be treated as delivery evidence. Each transition needs an owner and a recovery state.

Two Robots Must Create Two Safe and Independent Service Lanes

Putting two robots in one cabinet does not automatically double throughput. If both robots enter the same inventory aisle, wait for the same lift, or deliver through one shared pickup door, the software will spend much of its time preventing collisions. Worse, a jam on one side may stop the whole island.

The preferred starting point is two bounded service zones. Side A has its order queue, robot, delivery path, sensors, pickup port, and fault state. Side B has the same. Inventory can be physically separate, or a shared stock design can use controlled transfer points that never allow both robots into the same unsafe space. The choice affects capacity, refill labor, duplicate stock, and cabinet width.

Concurrency must be part of the factory test. Run both sides at once with different SKUs, different payment timing, and deliberate faults. Open a service door on side A and confirm the agreed response on side B. Interrupt one robot controller and verify whether the healthy side can continue. Restart after a command timeout and prove that neither order is delivered twice.

Cosmetics and Perfume Need Product-Specific Handling

A robotic island may carry lipstick cartons, foundation bottles, palettes, skincare jars, boxed perfume, and gift sets. Their width, height, weight, center of gravity, surface finish, and fragility vary widely. A gripper that works well on a square lipstick carton may squeeze a thin gift sleeve or lose a tapered perfume package.

Before mechanical design, the buyer should provide representative samples and the minimum and maximum package envelope. OBO can then evaluate suction, parallel gripping, tray transfer, bins, adjustable lanes, or a hybrid arrangement. Fragile glass products usually justify a controlled no-drop path with a supported handoff into the pickup area. Our robotic no-drop dispensing guide explains why a slow, verified handoff can be more valuable than a fast fall.

The machine should also confirm delivery with more than a motor-complete signal. Depending on the mechanism, evidence may come from robot position, grip or vacuum feedback, product detection at transfer points, pickup-door state, or a camera used for machine verification rather than customer identification. No single sensor proves every failure mode, so acceptance tests should use the actual package range.

Eight Brand Bays Need a Configuration Model

Four bays per side create a strong commercial format because each brand can receive a clear visual zone. The software still needs to know what a bay means. A bay record can include brand assignment, permitted SKU range, mirror catalog, campaign assets, language content, lighting profile, pricing source, inventory locations, and start and end dates.

That structure allows a brand change without rebuilding the whole interface. A seasonal brand can replace a permanent one; the new catalog, graphics, shelf props, and SKU map are deployed together. The dashboard should show which version reached each screen and mirror. If a new campaign downloads but its products are not stocked, the island should not present a purchasable look that cannot be fulfilled.

Physical modularity matters too. Header panels, shelves, mirror bezels, and graphics should be replaceable from a service position. Permanent holes and custom metalwork for every campaign make an otherwise intelligent retail system surprisingly inflexible.

One AI Mirror per Bay Changes the Cost and Support Model

An AI virtual try-on mirror is not only a reflective screen. A typical bay may need a display, camera, controlled lighting, compute or browser endpoint, catalog data, shade assets, API or SDK, analytics, content management, and a provider license. Eight mirrors multiply the endpoints, but the license model might be per device, per location, per session, or enterprise-wide. The quotation needs the actual model.

Public platforms show that beauty try-on can be delivered through APIs, kiosks, and in-store mirrors. For example, Perfect Corp publishes beauty AI APIs, while Banuba describes virtual try-on mirror software. These are market references, not a statement that either company is the committed partner for an OBO project. The selected provider has to confirm device compatibility, regional service, catalog onboarding, license terms, and data processing.

The machine supplier can integrate the mirror hardware and agreed software. The beauty-technology provider usually owns its underlying models and platform. The retailer or brands provide product data, approved shade assets, and merchandising rules. Put those roles in writing. Otherwise a “mirror included” line can conceal an annual license, onboarding fee, API volume charge, or unsupported catalog.

Virtual Try-On Accuracy Depends on Catalog Preparation

A mirror can render a polished effect and still point to the wrong product. The operational chain is shade asset to virtual result to sellable SKU to physical inventory. Product codes, shade names, regional assortments, campaign dates, and discontinued items need governance. Lighting around the camera also matters because unstable color temperature can change the customer’s perception.

The pilot should test representative skin tones, glasses, facial hair where relevant, head movement, varied store lighting, and the actual cosmetic categories in scope. A lipstick overlay is not the same technical problem as foundation matching or skin analysis. Avoid medical or diagnostic claims unless the specific system, evidence, and regulatory position support them.

Decide what happens to images. The privacy-friendly default for a live mirror is often local or transient processing with no saved face image unless the shopper explicitly chooses and understands a sharing feature. If photos, profiles, or analytics are stored, the project needs consent, retention, deletion, access, security, and vendor-processing rules appropriate to the market.

Arabic Support Must Be Native Right-to-Left Behavior

Arabic localization is easy to underestimate. Replacing English strings with Arabic text does not make an interface right-to-left. Navigation order, alignment, icons, progress direction, drawers, tables, receipt layout, error messages, and mixed Arabic-English product names need deliberate behavior. Numbers, prices, model codes, email addresses, and card references may remain left-to-right inside an Arabic sentence.

The W3C’s internationalization guidance explains that Arabic is predominantly right-to-left and that language and direction metadata need to be set correctly. Its internationalization quick tips and Arabic layout requirements are useful implementation references.

Test every surface: welcome screen, catalog, try-on controls, basket, payment prompts, collection instructions, out-of-stock states, support messages, operator login, refill app, reports, and printed or digital receipts. Arabic, English, and French should also share one product master rather than three separately maintained catalogs that drift apart.

Two Payment Terminals Need Local Acquirer Approval

The buyer may reasonably ask for card, contactless, Apple Pay, or Google Pay on each side. The machine manufacturer should not promise a terminal merely because it has integrated that model in another country. Production acceptance depends on the local acquiring bank or payment provider, merchant account, terminal application, currency, communications, unattended-use approval, and settlement arrangement.

The PCI Security Standards Council lists unattended payment terminals as a PTS device category and encourages merchants and acquirers to select approved devices. PCI approval alone does not make a terminal commercially usable with every Lebanese bank. The local acquirer still has to confirm the exact model and software.

Freeze the terminal only after that confirmation. Then the cabinet can be designed around its dimensions, mounting, service access, network, power, and security requirements. Side A and side B need separate order and terminal references. The payment API integration guide describes the states that should connect authorization, robot delivery, capture or reversal, receipt, refund, and reconciliation.

POS and Inventory Integration Needs More Than a Sales Export

A department store may expect the island to use its prices, promotions, tax logic, loyalty identifiers, stock records, and financial reconciliation. Start by deciding which system is authoritative for each field. If both systems can change price, conflicts are inevitable. If the island sells while the store system is unavailable, the recovery and reconciliation rules need to be explicit.

A practical API scope can include product and price import, available-to-sell inventory, order creation, payment reference, robot result, collection confirmation, refund, stock adjustment, alert, and daily reconciliation. Webhooks should be signed, retried, and deduplicated. Every order needs one stable identifier that appears in the customer interface, payment provider, robot event, island dashboard, and store system.

Ask for a sandbox or simulator before the finished island ships. The store’s integration team should not wait until factory acceptance to see the first API response. The platform boundary, logs, monitoring, and incident responsibilities also belong in the support agreement.

The Dashboard Should Separate Retail, Stock, and Technical Work

One back office can serve several teams without giving all of them the same permissions. Brand managers need campaign and bay performance. Store operations need stock, sales, refunds, and replenishment. Technicians need robot faults, door states, controller health, mirror endpoints, payment connectivity, and logs. Finance needs settlement and reconciliation, not robot motor data.

Useful alerts include low stock, failed or unconfirmed pick, pickup not collected, bay unavailable, robot offline, mirror application unavailable, payment terminal offline, door open, temperature where required, UPS event, and integration backlog. An alert should create a next action and preserve its history. A wall of red icons with no owner is not remote management.

The fragrance vending platform guide explains the same operating principle for a different premium retail category: the software record has to agree with the serviceable physical machine.

Planning note: this existing OBO beauty-vending workflow is a general activation framework. A robotic retail island adds AI catalog governance, dual-side concurrency, department-store integration, and more detailed FAT requirements.

Footprint Comes From Capacity, Reach, and Service Clearance

A supplier should propose a department-store footprint, but a credible dimension cannot be selected from appearance alone. Capacity by SKU, refill frequency, product envelope, robot reach, mirror width, customer circulation, accessibility, service doors, ventilation, structural stiffness, and packing constraints all influence the plan.

A long narrow island can display four bays clearly on each side, yet it may force the robots to travel too far. A deeper island can improve stock density and service access but consume valuable floor space. End-mounted touchscreens can free the bays visually, while central screens may shorten customer walking. These are layout trades, not styling preferences.

Request at least a top view, customer-side elevations, service-side clearances, maximum door swing, center of gravity, total mass, floor loading, power and network entry, ventilation zones, and installation path. Confirm elevator, doorway, loading dock, and final assembly constraints at the destination before the cabinet is packed.

Power Quality Requires a Defined Recovery Strategy

If the destination uses 220 V / 50 Hz and experiences voltage fluctuation, the project can include surge protection, voltage regulation, monitoring, and a UPS. The right design depends on the measured site conditions and the desired outcome. Keeping eight mirrors and two robots running for an hour is very different from providing enough time to finish or safely cancel active orders, park the robots, save records, and shut down controllers.

The load schedule should include both robots at peak acceleration, displays, mirror compute, payment terminals, controller, lighting, networking, fans, and any thermal systems. Startup current and power-factor behavior may matter. The machine also needs an agreed response to brownout, repeated interruption, UPS low battery, and restoration. Automatic restart is convenient only when the robot can re-establish its position and order state safely.

During FAT, interrupt mains power at idle and during representative operations. Verify safe stopping, no trapped product, transaction recovery, log integrity, and restart. A UPS brand name in a quotation is not a substitute for this test.

Safety and Accessibility Belong in the Industrial Design

Robots should remain behind interlocked panels during customer operation. Pickup doors need anti-pinch behavior and a geometry that does not expose moving equipment. Service doors should have controlled access, clear isolation points, and maintenance positions. The island should resist tipping, unauthorized opening, and foreseeable impacts from carts or floor equipment.

The customer interface, payment terminal, pickup opening, and mirror controls need heights and reach ranges suitable for the intended users and local requirements. Glare, camera angle, screen readability, audio use, and clear collection instructions matter in a busy beauty floor. Emergency behavior should be understandable to store staff who are not robot technicians.

Product safety is also part of the machine. Fragrance packaging, cosmetic shelf life, batch or expiry information where needed, storage temperature, leakage containment, tester hygiene, and recall procedures should be planned with the brands and retailer.

CE Is a Compliance Process, Not a Generic Certificate

A buyer may request CE or other certificates. The supplier first needs the destination markets, final electrical design, radio modules, robot system, payment devices, and responsibility for the assembled unit. The applicable requirements may involve machinery safety, electrical safety, electromagnetic compatibility, radio equipment, material restrictions, and local rules. Not every document applies to every configuration.

The European Commission explains that the manufacturer is responsible for identifying applicable EU requirements, completing the conformity assessment, preparing technical documentation, and affixing CE where harmonized rules require it. See the official CE marking guidance. Lebanon is not the EU, so the importer and local professionals should also confirm Lebanese requirements and any department-store standards.

Ask for a compliance matrix, not only a logo. It should identify the final product configuration, standards or regulations considered, test reports, declarations, labels, manuals, responsible manufacturer, and limitations. Changing a robot, power supply, radio, or cabinet structure after testing can affect that evidence.

A Turnkey Price Needs an Explicit Bill of Responsibility

“One complete working unit” is a reasonable request. The quotation should still show enough detail to reveal assumptions. A useful breakdown separates main cabinet and finish, two robotic systems, inventory fixtures and grippers, eight mirror hardware sets, AI platform setup and licenses, two touchscreens, two payment-terminal integrations, local controllers, cloud dashboard, POS API work, multilingual UI, networking, UPS or stabilizer, testing, packaging, documents, spare parts, travel, installation, and training.

Mark every line as included, optional, buyer-supplied, third-party direct, provisional, or excluded. For recurring items, show the billing unit and renewal owner. AI mirror fees, cloud hosting, cellular data, payment processing, remote support, software maintenance, and certificate renewal should not hide inside an unexplained annual fee.

The quotation comparison and TCO checklist helps buyers compare systems that appear similar in the first-year total but allocate software, integration, freight, and support very differently.

EXW, FOB, and CIF Prices Are Not Interchangeable Totals

Each quotation should name the place or port and the Incoterms version. EXW at the factory, FOB at a named Chinese port, and CIF at Beirut do not transfer cost, responsibility, and risk at the same point. Packaging, inland transport, export clearance, ocean freight, insurance, destination charges, import duty, VAT, customs brokerage, unloading, and final delivery need separate treatment.

The International Chamber of Commerce publishes the official Incoterms 2020 framework. ICC also notes that FOB and CIF are maritime rules, while other terms may fit containerized or multimodal transport better depending on how delivery occurs. The buyer and freight professional should select the term rather than using familiar abbreviations automatically.

A large retail island may ship as modules in reinforced crates. The packaging plan affects container space, insurance, handling, installation labor, and the risk of cosmetic damage. Request packed dimensions and weights, crate count, center-of-gravity or lifting instructions where needed, moisture protection, shock indicators if used, and a photo record before dispatch.

HS Codes Should Be Proposed, Then Confirmed by the Importer

A custom island combines vending functions, computing, display, payment, robotics, and furniture-like structures. Customs classification depends on the essential character, configuration, shipment method, and local tariff interpretation. Supplying one confident code before the design is fixed can create false certainty.

The supplier can provide a proposed code, product description, component list, invoice details, and supporting literature. The Lebanese importer or customs broker should confirm the final classification before shipment. If modules ship separately, some components may be classified differently. Record who made the determination and which configuration it covers.

Intellectual Property Needs Four Separate Conversations

“Who owns the design and software?” is too broad for a useful answer. Separate background technology, project-specific work, third-party services, and operational data.

• Background IP: existing robot controls, machine libraries, dashboard modules, manufacturing methods, and reusable hardware usually remain with their original owner.
• Project-specific deliverables: agreed exterior design, graphics templates, UI assets, interface documents, drawings, and custom code should be listed with ownership or license rights.
• Third-party IP: AI mirror engines, payment applications, fonts, and licensed components remain subject to their provider terms.
• Business data: products, sales, stock, campaigns, users, and service records need clear access, export, retention, and exit rights.

Source-code delivery is not the only continuity model. Alternatives include a perpetual deployment license, documented APIs, configuration export, source escrow triggered by defined events, replacement-part rights, and a transition-assistance clause. The correct arrangement depends on what is custom and how much the buyer funds. Our software, data ownership, and SLA checklist provides the questions that should reach the contract.

An NNN Agreement Should Protect Real Confidential Information

A supplier can review a mutual confidentiality and non-use agreement before receiving detailed drawings. The agreement should identify the parties, confidential material, permitted evaluation and manufacturing use, exclusions, disclosure to employees or approved subcontractors, security, return or destruction, term, remedies, and governing law. It should also allow the supplier to keep using independently developed background technology.

Do not send detailed drawings only to discover later that a required mirror provider, payment partner, or robot subcontractor cannot see them. The disclosure path needs to match the actual project team. Both parties should obtain appropriate legal advice; an article or sales email is not a substitute for counsel.

Live-Video FAT Can Be Rigorous When the Script Is Agreed Early

A live video is useful when it follows a written acceptance matrix and shows unedited evidence. Start with machine identity, software version, dimensions, finish, labels, and safety devices. Load an agreed SKU map, then run normal picks on both sides at once. Include the largest, smallest, heaviest, most fragile, and least rigid packages.

Continue with failure cases: unavailable SKU, failed grip, blocked pickup, door open, one robot offline, one payment terminal offline, network interruption, duplicate API event, mirror unavailable, and power loss. Show the Arabic RTL customer journey, English and French switching, payment test environment, POS messages, stock update, refund or reversal logic, alarms, and dashboard records.

Close with service access, replenishment, cleaning, robot recovery, log export, spare parts, manuals, accessories, crate preparation, and punch-list ownership. The factory acceptance test checklist can be adapted into the project-specific script.

Installation in Lebanon Needs a Named Handover Plan

A machine can be factory-tested and still fail at the site because the floor, power, network, payment account, lifting route, or POS credentials were not ready. Use a site-readiness document before shipping. Confirm final position, access route, floor capacity and anchoring, electrical feed, grounding, network, firewall, local bank terminal, store API environment, working hours, permits, and installation contacts.

On-site installation can be quoted when travel, visas, schedule, local labor, and retailer access are known. A remote-guidance model can work with a competent local technician if the unit is modular, cables are keyed and labeled, lifting and alignment are documented, and live support is scheduled. Decide who supplies tools, lifting equipment, consumables, internet access, and acceptance sign-off.

Training should cover store operations, replenishment, campaign changes, refunds, routine cleaning, daily checks, alarm response, robot recovery, payment support boundaries, and escalation. Record the training and leave role-specific manuals rather than one generic PDF.

Warranty and Spare Parts Should Match the Support Geography

A warranty needs a start date, duration, covered parts, exclusions, labor treatment, remote diagnosis process, response targets, shipment terms, and responsibility for third-party components. An AI platform license, payment terminal, industrial PC, robot, mirror display, and custom cabinet may have different supplier warranties. The turnkey seller should explain how one support ticket will be coordinated across them.

The pilot spare-parts proposal can include critical sensors, pickup-door components, cables, power supplies, fans, control boards, robot wear items, fasteners, touch or display spares where practical, and cosmetic finish materials. Prices, lead times, shelf life, and replacement skill should be listed. Expensive assemblies may remain at the factory with an advance-replacement process instead of sitting unused on site.

Our after-sales and spare-parts guide helps turn a broad warranty promise into a service model the retailer can actually use.

Company Evidence Must Respect Other Clients’ Confidentiality

A serious buyer can request a business license, factory information, quality documents, machine photos, demonstration videos, and relevant export experience. Similarity should be described honestly. A single-sided fragrance cabinet is relevant evidence for product presentation or payment, but it is not proof that an eight-bay dual-robot island already exists.

Client references require permission. A supplier should not reveal another customer’s contact details, drawings, commercial terms, or project video simply to satisfy a new RFQ. Alternatives include redacted case material, live factory demonstrations, permission-based references later in the diligence process, and evidence of subsystem capability.

This balance matters. A supplier that protects existing customers’ confidential information is more likely to protect the new buyer’s drawings too.

One Pilot Followed by Two Units Is a Sensible Stage Gate

A first unit should settle the architecture and expose operating realities before two more copies are ordered. Define success before production: simultaneous throughput, pick success by package family, mirror availability, payment completion, POS reconciliation, stock accuracy, replenishment time, interface usability, incident rate, service response, and shopper conversion where the retailer can measure it responsibly.

The pilot should also identify what can be standardized. Cabinet structure, robot interfaces, device identity, software release process, API, electrical design, mirror mounting, payment cutout, and spare-parts list should become a controlled baseline. Brand graphics, assortment, language content, and some bay fixtures can remain configurable.

After a defined operating period, review failures and service notes, then freeze the changes for units two and three. Scaling too quickly preserves prototype problems. Waiting without collecting evidence wastes the pilot.

What to Send for a Quotable Proposal

Area	Buyer information	Why it matters
Products	SKU list, package dimensions, weights, fragility, samples, capacity, and refill frequency	Robot, gripper, storage, and pickup design
Brand bays	Four brands per side, fixture expectations, campaign change frequency, testers, and lighting	Modular merchandising and content configuration
Try-on	Categories, provider preference, catalogs, privacy rules, analytics, and license expectations	Mirror hardware, AI integration, and recurring cost
Languages	Arabic, English, French copy owner, currency, receipts, and terminology approval	RTL implementation and localization acceptance
Payments	Lebanese acquirer, merchant account, required methods, terminal candidates, refunds, and settlement	Terminal selection and production workflow
Store systems	POS, ERP, inventory, API documents, sandbox, ownership of prices and stock, and security	Integration scope and reconciliation
Site	Floor plan, customer circulation, installation route, power quality, network, access hours, and store standards	Footprint, utilities, packaging, and deployment
Commercial	Incoterm and named place, target schedule, warranty, support, software term, IP, and pilot success gate	Comparable turnkey quotation and contract

With that information, the supplier can propose a preliminary footprint, system block diagram, responsibility matrix, interface list, phased schedule, price breakdown, and assumptions. Detailed industrial drawings can follow the agreed confidentiality process.

A Practical Turnkey Position

A turnkey offer is achievable when the word means “integrated to a written boundary.” It does not mean every third-party service becomes the machine manufacturer’s intellectual property, that any terminal works with any bank, or that a conceptual rendering proves the robot path.

The strongest proposal will identify one accountable integrator while keeping responsibilities visible. It will show how two customers can be served safely, how every try-on shade reaches a stocked SKU, how Arabic works through the whole journey, how local payment is approved, how store systems reconcile, what survives an outage, what recurring licenses cost, and what the FAT proves before shipment.

That level of clarity is more valuable than an early low number. It gives the buyer a pilot that can be operated, supported, and repeated if the first department-store installation succeeds.

Related Custom Retail Automation Resources

• cosmetics vending machine project planning guide
• beauty vending machine buyer guide
• robotic no-drop dispensing guide for glass fragrance products
• luxury fragrance retail terminal development guide
• luxury fragrance vending platform software guide
• vending machine payment API integration guide
• software, data ownership, and SLA checklist
• factory acceptance test checklist
• quotation comparison and total-cost checklist
• after-sales, warranty, and spare-parts planning guide
• custom vending machine export certification guide

Frequently Asked Questions

Can a double-sided cosmetics retail island serve two customers at the same time?

Yes, if each side has an independent order state, payment terminal, delivery path, robot work envelope, pickup area, and fault isolation. Two robots sharing one uncontrolled aisle can create collisions and ambiguous orders, so concurrency has to be designed and tested rather than assumed from the robot count.

Can the user interface support Arabic, English, and French?

Yes, but Arabic support is more than translated labels. The interface needs right-to-left layout behavior, appropriate fonts, mixed Arabic and Latin data handling, localized numbers and currency, mirrored navigation where appropriate, and testing on every customer, service, receipt, and error screen.

Is an AI virtual try-on mirror normally included in the machine price?

It can be included in a turnkey proposal, but the quotation should separate mirror hardware, camera and lighting, software integration, product-catalog preparation, initial setup, and recurring provider licenses. The machine supplier should not imply ownership of a third-party AI platform unless that relationship and license are documented.

Can the retail island connect to a department store POS and inventory system?

Yes, when both parties agree on the API scope. Typical interfaces cover product and price synchronization, stock availability, order creation, payment references, dispense results, refunds, sales export, alerts, and webhooks. The pilot should test duplicate events, outages, retries, and reconciliation, not only the happy path.

Will any unattended card terminal work with Lebanese banks?

No. The terminal model, payment application, acquirer, merchant account, network, currencies, and unattended approval must be accepted for the target market. The local bank or payment service provider should confirm the production terminal before the cabinet cutout, cable interfaces, and software workflow are frozen.

Can a UPS or voltage stabilizer be installed?

Yes. The power design can include surge protection, voltage regulation, and a UPS sized for a controlled stop or a defined operating period. The load calculation must include both robots, screens, mirrors, payment devices, controller, lighting, network equipment, and startup current before the UPS is selected.

What should a live-video factory acceptance test cover?

It should cover both sides operating concurrently, SKU mapping, successful and failed picks, fragile products, payment and refund states, Arabic RTL screens, mirror launch and catalog mapping, POS or API events, network loss, power recovery, alarms, service access, documents, labeling, packaging, and the agreed cycle count.

Discuss a Robotic Cosmetics Retail Island

Send representative product samples or dimensions, capacity targets, preferred brand-bay layout, AI try-on scope, site plan, language content, local acquiring contact, store API documents, power conditions, pilot schedule, and commercial requirements. OBO can then review the robot architecture, island footprint, integration boundary, quotation blocks, FAT, packing, installation, and support plan as one project.