Menu Management & Support

Who we are

NOAHS is a Danish commerce-technology company. We build and run the systems that convenience-retail and forecourt operators sell through — live today in 120+ locations across Denmark, Belgium and Ireland, and expanding. You would be employed by Noahs TH Co., Ltd., our BOI-registered Thai entity in Bangkok. The team is small, senior and remote-first; the wider company spans Thailand, Denmark, Belgium, Ireland and India.

Before you apply, spend ten minutes finding out what we actually sell and who we sell it to. We ask about it at interview, and it is one of the more revealing questions we ask — not as a memory test, but because the people who do well here are the ones who were curious before anyone asked them to be.

The role

You own what customers see when they order, and you fix it when it breaks. Every product, price, combo, promotion and opening hour on every ordering surface we run — kiosks, apps, web, delivery marketplaces and in-store tills — is configured by a person. That person is this role. When a price is wrong at a till in Denmark, when an item is sold out but still orderable, when a store opens on a public holiday and the system does not, it lands with you.

This is catalogue operations on live retail systems, not a helpdesk. The work is precise, it is visible to customers within minutes, and it is wrong in ways that cost money.

What you will actually work on

• Building and changing live menus — products, categories, modifiers, combos and meal deals, each with its own identifier, price and tax treatment, across several ordering channels that each behave slightly differently

• Prices and promotions on a monthly campaign cycle, plus the urgent one-off that has to be live before the store opens tomorrow

• Availability — taking items off sale everywhere at once, and working out why something marked sold out is still being ordered

• Opening hours and scheduled open/close, per channel, per site, including the holidays that break every assumption

• Country-specific rules — tax that varies by item and by market, deposit schemes, licence restrictions that make some products unsellable on some channels• Incidents — a till not printing, orders not reaching a kitchen screen, a channel silently offline — diagnosed to root cause, not just cleared

• Getting third parties to fix what is theirs, with enough evidence attached that they cannot send it back

Responsibilities

Menu and catalogue management

• Build, change and publish catalogues across every channel a site sells through, and verify on the front end that what you published is what arrived

• Own identifier and price integrity — no duplicates, no orphans, no item priced at zero

• Run the recurring campaign and assortment cycles to their deadlines, and absorb the ad-hoc requests around them

• Apply tax, deposit and licence rules correctly per market

Support and incident resolution

• Acknowledge every new ticket within one hour — “working on it” counts; silence does not

• Diagnose to root cause and classify it; “it works now” is not a resolution

• Close every ticket with two written records: a technical account for us, and a plain-language reply for the customer

• Make contact with the store, by phone if needed, rather than closing on an assumption

Monitoring and reliability

• Watch device, channel and location health, and open the ticket before the customer does

• Take a weekend and public-holiday support rota alongside the rest of the team Partners, documentation and reporting

• Raise and chase issues with third-party providers with the specifics attached, and escalate when a timeline slips

• Write up what you learn into the knowledge base so the next person does not re-derive it

• Report on what is open, what is recurring, and what is at risk

Requirements

• At least 2 years in a role where you configured live production systems that customers or staff depended on — retail, hospitality, e-commerce, POS, ERP, telecoms, logistics. What matters is that real people felt it when you got it wrong, not the industry

• Genuine comfort in spreadsheets — lookups, matching two lists, spotting the twelve rows that differ. A large part of this job is reconciling one system’s export against another’s import• Structured diagnosis. You can take “it’s not working” and turn it into a reproducible fault with a cause, rather than restarting things until it stops

• Precision under repetition. The work is detailed, it repeats, and a transposed digit reaches a customer. We will test this

• Working English, written and spoken. The team spans Thailand, Denmark, Belgium, Ireland and India, and every customer-facing reply you write is read by someone in Europe. You need to explain a technical situation clearly, in writing, to someone who is not technical

• Thai for day-to-day team communication

• Able to work unsupervised. The team is small and there is no capacity for close guidance

On years of experience. Two years is a guideline, not a filter. The list above describes what the job needs, and a year count is a rough proxy for it. If you are short and still think you can do this, apply and make the case — tell us what you have configured, and what broke when you got it wrong.

Preferred

• Agentic AI tools in daily use — Claude, Copilot, Cursor — with a verification habit. We are AI-heavy, our support tooling is AI-assisted by design, and we check everything it produces

• Experience with point-of-sale, kiosk, or delivery-marketplace platforms

• Having worked a rota, an on-call, or a shift covering another continent’s business hours

• A European language, Danish especially — customer replies go out in the customer’s language first

• Basic SQL, or comfort reading an API response and telling which side is wrong

• A Windows machine. Parts of our stack are still Windows-only and are being retired; until they are, Windows makes a few things easier. Not a barrier if you work on a Mac

What you would be signing up for

Read this part twice. People who take the job on a wrong picture of it leave, and that is expensive for both sides.

• You work European hours from Bangkok. Our customers’ day starts when ours is ending. Support runs from early morning to midnight CET, seven days a week, and this seat covers a shift inside that window — not a Thai nine-to-five

• A weekend and public-holiday rota. Live customer-facing systems in several countries; something will break outside office hours, and some of those hours are yours

• Repetitive, exacting work with real consequences. This is not a role that becomes less detailed as you get senior in it. It becomes faster and more accurate• An incomplete knowledge base you are expected to fill in, not to be onboarded from

• You will be blamed for things that are not your fault, because you are the visible end of a chain that includes other companies’ systems. The job is to prove where the fault is, calmly, with evidence

• Not a development role. You configure systems; you do not write code to fix a data problem. If you want to be a developer, this is the wrong seat and we would rather you said so now

If none of that puts you off at all, you have probably not read it closely. We would rather hear which part concerns you.

Working here

• Salary: THB 33,000–37,000 per month depending on experience, with room above the range for an exceptional candidate

• Hours: 44 hours a week — 8–9 hours a day Monday to Friday, with any shortfall made up on Saturday. Your daily window is shifted late to overlap Europe; see above

• Employment under Noahs TH Co., Ltd. — full Thai labour protection, health insurance and social security

• Remote, with one scheduled in-person day per week

• Reports to the Support Lead, within a small support and systems team

• We build and support with AI deliberately. Bring your own practice; we will not police the tool, only the verification

How to apply

Please include, in the application itself:

1. Expected monthly salary

2. English level — a test score if you have one, an honest self-assessment if you do not

3. A short answer to this: describe a time you changed a live system and it went wrong. What broke, how did you find out, and what did you do? We are not looking for people who have never broken anything — we are looking for how you handle it.