Frequently asked questions.

No. Content is stored on the device and keeps playing.

Yes. Manage screens across all stores from a single console.

Yes. The LUMA AI CMS Menu Board uses the same menu data as LUMA POS. When you edit a price or mark an item sold out, it is automatically published again shortly afterward to the Store Screens that show that item, and discounted items are shown with the original price struck through.

Yes. Set a Schedule with day-of-week, time-of-day and date-range rules, and the Screen changes by itself at the set time. Late-night schedules that run past midnight are also supported, and in the console you can see at a glance what content is showing right now and why.

Yes. Emergency Publish instantly shows a notice on all the Screens you select. It is confirmed with the manager's PIN and a record is kept, and when you cancel it, each Screen returns to its original schedule. The notice also goes out to video wall Screens.

You can upload photos in JPG, PNG, WEBP, GIF and SVG up to 50MB, and videos in MP4, WEBM and MOV up to 2GB. Uploaded videos are automatically optimized so they play well on Store Screens. Please convert iPhone photos (HEIC) to JPG before uploading.

Yes. Set the off time and on time for each day of the week, and the box turns the Screen off at that time and turns it back on by itself at the set time even while it is off. You can also turn on a regular reboot if needed.

Yes. Configure it as a 2×2, with one media box connected to each screen.

Bezel calibration is coming soon.

Supports up to 4 across and 4 down, 16 screens in total.

Yes. The LUMA box connected to each Screen plays its own part of the video, and the boxes synchronize their clocks with each other over the Store network. For a wide video spanning several Screens, the server splits it into per-Screen pieces in advance and sends them to each box, so no separate controller is needed.

No, they won't. The boxes set a shared clock over the same in-Store network, so they play together even without the internet, and during playback they keep measuring any drift and correct it gradually. Videos are stored on the boxes and played from there, and the video wall restores itself after a reboot.

Yes. There is a clone mode in which several Screens play the same video at the same moment without splitting it. Synchronized schedule rotation is also supported, which cycles through several pieces of content for a set length each, with all Screens advancing together.

Just upload a regular video. Even a wide video spanning several Screens is cut by the server into FHD pieces for each Screen and sent out, and once split, the pieces are stored so they go out immediately when published again. Photo, text and Menu Board Screens made in the CMS editor can also be put on the video wall.

Yes. In the LUMA AI ad maker, choose one of background, product composite, concept image, typo banner or poster, then just enter a topic or text. If wording is hard, you can write what you want to say freely and leave it to the AI, and images are created in landscape or portrait Screen sizes.

Yes. In the ad video wizard, upload product photos, choose an art style and a narrative, and write a brief. The AI then drafts a scene-by-scene scenario and creates the video. The AI checks each scene against the product you uploaded, and you can pick only the scenes you don't like and recreate them.

You can set the ad length anywhere from 5 to 60 seconds, and the finished video is produced in landscape FHD (1920×1080). The AI does not draw subtitles and text as part of the image. They are added as exact text at the final stage, so the characters never come out garbled.

When AI-generated images or videos appear on a store screen, an “AI Generated” label is added automatically in the store's language, and AI-generation information is also recorded inside the video file. If your company policy does not allow external AI, an administrator can turn off external AI use in the Organization settings.

Yes. Once you send a finished image or video to the Media Library, you can add it straight to a Playlist or Schedule in LUMA AI CMS and publish it to your Store Screens. For urgent items such as a discount banner, you can also show it right away with emergency Publish, or you can simply download the file and use it elsewhere.

Yes. Send a share link for a specific ad, and they can view that ad's report only, without logging in. No other ads or device info are shown.

Ad attention analytics, used together with LUMA Vision, is in preparation for launch.

Yes. Each time the LUMA box in a store plays content, it records the start and end times on its own and uploads them. Reports calculate impressions, play time, number of stores that showed the ad, and completion rate from these records alone. Even if the same record is sent several times or plays overlap, it is counted only once, so the numbers are never inflated.

No. Records from the time of the outage are saved on the device and uploaded once it reconnects. They are deleted from the device only after the server confirms they have been saved. Any time the device was powered off is shown separately as a “No-record period”.

Every share link has an expiration date. The default is 90 days, and you can set it up to 365 days. When a contract ends, you can revoke a link with a single button, and a revoked link will not open even if someone knows the address. You can also see the view count and the date each link was last opened.

The prepaid and postpaid payment flows and the approval, cancellation, and refund handling are ready, while actual integration with card companies and payment providers is in preparation. Cash payments, refund handling, and the sales ledger are available now. For the schedule of payment terminal integration, please ask through the purchase inquiry.

Yes. When you upload a photo of a paper menu or an Excel table, the AI reads the menu names, prices, and categories and shows them in an approval table. Only the items you review and approve are added to the menu, and you can also edit directly in the table as in Excel or paste in data.

Yes. Every time a sale, refund, or cancellation occurs, a ledger by payment method and tax type is built up automatically, and we provide a VAT screen and CSV export. For direct integration with a specific accounting or ERP program, please ask through the purchase inquiry.

Yes. You can assign a menu created by headquarters to multiple stores and adjust prices and visibility separately for each store. Changes are kept in the change history, and the counter, kiosk, and Menu Board all use the same price calculation, so prices never differ from screen to screen.

When the AI explains today's sales trends in sentences, it attaches the numbers each sentence is based on, and sentences without supporting figures are filtered out. Patterns that differ from the usual, such as continuing cash drawer discrepancies or a cluster of late-night cancellations, are raised as anomaly alerts, and the Store can turn the rules and threshold values on or off and change them.

LUMA table and QR ordering is coming soon. The 10-inch table device screen that sits on the table is in preparation, and we will provide the official release schedule and pilot adoption details through the purchase inquiry.

No. When a customer scans the table QR with their phone camera, that table's order screen opens right in the browser, and no sign-up is needed. Customers can choose their own language from 6 languages. Table order is coming soon.

Yes. Orders that come in through the same table QR are grouped into one table with a single total, and payment is also settled at once per table. QR ordering defaults to pay-after: orders are taken first and paid at the counter. Table order is coming soon.

Kiosk, QR and counter orders appear on the kitchen display (KDS) within seconds, with the table number and a dine-in/takeout label. The kitchen moves each order through three steps: New order → Cooking → Done. When an order is marked Done, its number appears on the call board and is also announced by voice. The kitchen display can also be operated with a remote or a keyboard.

The payment step screens and the prepaid/postpaid flows are ready, but actual card payment is still being prepared, pending integration with the payment provider and terminal. For now, you take orders at the kiosk and customers pay at the counter. Please ask us about the rollout schedule through an adoption inquiry.

Yes. The kiosk supports Korean, English, Japanese, Chinese, Spanish and German screens, and the store chooses which languages to offer and in what order in the console. Menu names and descriptions are translated with the AI menu language pack, but only translations approved by the store are shown to customers. You can also set the store name for each language.

It offers a low-screen mode that lowers the entire screen, a large-text mode that enlarges text by 1.25 times, and step-by-step voice guidance. If a customer walks away, the kiosk doesn't rush them: it asks calmly and then returns to the first screen. The store can lengthen the waiting time.

Saved menus stay visible so the screen never goes blank, but order confirmation is blocked until the connection returns, and the kiosk tells customers to call a staff member. This is to prevent orders from silently disappearing. Once the connection is back, customers can place orders again automatically.

Yes. You issue percentage and fixed-amount coupons in the console, and customers use them by holding a QR code up to the kiosk scanner or entering a number. Points can be earned and used with a phone number; the phone number is converted to an irreversible value before it is stored, and consent is collected separately. When a customer signs up as a member, you can print a member slip with a QR code on it.

LUMA Vision is currently in preparation (private tier). We are developing it to provide anonymous statistics such as visitor counts, dwell time per zone and a heat map of the store floor plan. We will share the official launch schedule and pilot adoption through an adoption inquiry.

No. It is designed to process video directly on the device inside the store and send only anonymous numbers to the server. Video and audio recording cannot be turned on with any setting, and the store can also pause counting briefly if a customer asks.

No. It does not recognize people or re-identify the same person, and it does not record any individual's movement path. Numbers are kept only grouped by zone and time period. LUMA Vision is in preparation.

Yes. On supported terminals with a face camera, members and staff who have consented can check in and clock in with their face. Face data is kept encrypted inside the terminal and is not stored on LUMA servers. Anyone not enrolled keeps using phone QR, manual check-in at the counter or a staff PIN.

No. The member app opens in the phone's browser without an app store installation, and members simply add it to their home screen. The attendance QR refreshes at short intervals, so a captured screenshot passed to someone else won't work. Attendees who come only once just need a link or a printed QR.

Yes. The terminal checks Time memberships and Visit packs right away, and a Visit pack is deducted by one each time the member enters. If a Membership has ended, the terminal shows the reason, such as “Your period has ended”, and when a member passes through it shows the remaining visits. Places that only record attendance can be set to “Attendance only”.

Yes. Staff members enter their PIN on the same terminal and tap clock in, start break, end break or clock out. These records are kept separate from member attendance. When a record is corrected, the original is not deleted and a correction history is kept. After the monthly closing, that month's records can no longer be edited.

Member attendance is saved on the terminal first and uploaded automatically when the connection returns. It is deleted from the terminal only after the server has confirmed it was saved. Staff PIN clock-in/out is currently recorded only while connected, and when the connection is down, a message asks the staff member to try again.

When you register a Member, consent is collected using wording set by the Store, and when a Member withdraws, their personal information is deleted immediately. The retention period for Member attendance records can be chosen from 3 to 36 months (default 12 months), and only people with permission can export the attendance sheet, with a record kept each time it is done.

Change it in product editing in LUMA POS. The price tag shows the POS price as is, so you don't edit it on the price tag itself. That way the shelf and the checkout counter always use the same price. Even if the internet goes down, the price tag keeps showing the last price.

No. When you set up a discount, you choose an end date. On that date the price tags, checkout counter, kiosks and Menu Boards all return to the regular price together. During the discount, the previous price is shown with a strikethrough along with the discount rate.

Yes. Unit prices such as per 100g or per item, along with volume and country of origin, are shown next to the selling price. For meat, you can display fields for cut, grade and traceability number. Units such as lb and oz are supported, as well as multiple currencies such as dollars and pesos. You choose from more than 40 basic layouts and 11 color themes.

Currently, both the front and back sides show the same content. Showing different content on each side requires support on the device side, and it is in preparation.

On screens showing customer info, remote screen transmission and input are blocked.

Only people with store admin permission can perform remote control.

Yes. In the admin app, the device screen is shown on top and a touchpad below, and you use them to control the device. On site during installation, you can use Mouse mode, which turns a phone connected to the same Wi-Fi as the box into a mouse. Enter the 6-digit code shown on the box screen to connect.

No. The LUMA box connects to the LUMA server first, so you don't need to change any router settings to view and control the remote screen, restart, and manage files.

Yes. You can browse the list of files on the device and upload, download, rename and delete them, with up to 2GB per file. The system area the device needs to run is read-only by default, which prevents important files from being deleted by mistake. Remote file management requires Owner or Admin permissions.

The LUMA support team receives logs remotely, reviews them alongside AI Diagnosis results, and takes action.

Diagnostic logs are automatically deleted after 30 days.

It finds problems that leave traces in the logs, such as forced app closures, unresponsive apps, repeated reboots and out-of-memory shutdowns. The report shows the severity and confidence level, a one-line cause, the actual log lines used as evidence, and the steps to follow to fix it. If there is no evidence, it does not make anything up.

Phone numbers, emails, IP and MAC addresses, and credentials are masked by the server before the AI reads them. Sensitive lines that could identify a person are removed or masked by the device first, before it sends the logs.

If the cause is in the LUMA box app, the technical support team remotely installs a fixed version one device at a time. If an installation fails, it stops there and the device keeps running the previous version. The steps for the store to take are listed in order in the report, and from the same screen you can go straight on to remote control or a restart.