Resellers, franchise HQs, POS vendors — a 24/7 employee on top of every store
Resellers
How many store visits did you make this month?
The owner's PC handles kiosk calls and first-line complaints instead of you. Visit count drops, renewal rates rise — per-store commercial structure discussed in person.
POS + AI employee bundle — your edge vs other resellers
Store calls · first-line complaint handling automated
Demo kit — runs on a single laptop in the meeting
Per-store commercial structure — discussed in person
Do you actually know if your SOP runs at every store?
HQ can't physically visit every store. The WinClaw on each franchisee PC executes HQ-authored SOP and rolls real ground-truth back into HQ-side reports — contract structure discussed in person.
HQ SOP auto-runs at franchisees — no memorization required
Group reports — visibility into what was previously invisible
Consistency monitoring — verify each store matches SOP
Add "POS + AI employee" to your sales catalog without building the AI layer in-house. Delivery-app and Naver integrations also run together once WinClaw is installed — partnership structure discussed in person.
OK POS KR
Active collaboration
Menu recognition API together — from one photo to a new menu entry
WinClaw calls OK POS's menu recognition API so an owner can upload a single product photo and have prices, options, and combo composition extracted and registered as a new menu item on the POS — without ever bypassing the POS as the source of truth.
Owner input time per new menu: ~10 min → ~30 sec
OK POS remains the owner of all accounting/tax data; WinClaw only automates the input layer
Newly-registered menu syncs immediately to delivery apps + Naver Place (Channel Manager loop)
Union POS KR
In production — bidirectional sync
Two-way sync with the OQ app — change in one place, both stay current
Bidirectional sync between Union POS and the OQ app is live in production. Price changes on the POS reflect in OQ, and sold-out toggles in OQ propagate to POS inventory (currently minute-scale latency, being reduced). The owner experiences one system while accounting responsibility stays cleanly on the POS.
Bidirectional sync in production — minute-scale latency, reduction in progress
POS outage → OQ falls back to last-known state, reconciles on recovery
OQ-side changes mirrored to POS audit log for accounting review
MetaCity POS KR
Active collaboration
Menu recognition API together — a unified C/S workflow is in discussion
Menu recognition API collaboration with MetaCity POS is committed — photos/PDFs are auto-converted and registered into MetaCity POS format. On top of that, a unified C/S workflow (delivery-app reviews, DMs, ChannelTalk in one place with auto-drafted replies) is in active discussion.
Drafts pre-rendered so reply time shrinks (one-click post after review)
Order context (which menu, when, refund status) auto-included in draft
Multiple C/S channels (delivery apps, Naver DM, ChannelTalk, etc.) unified into one inbox
Toast / Square US · Global
Preparing for overseas expansion
G Company's US golf sports pub expansion — Toast (US) / Square (global) adapters in preparation
Discussions are underway around G Company's US golf sports pub expansion. We're preparing adapters for Toast (a major US restaurant POS) and Square (broadly adopted globally) so the Korean-store experience carries over abroad — the POS underneath swaps; the operating workflow stays identical.
Toast/Square adapters abstract menu sync, order flow, and settlement reporting behind one interface
Bilingual owner pages (KO/EN) — local managers at overseas stores use the same surface
Same pattern applies to Korean F&B franchises (Korean food, fried chicken, etc.) expanding abroad