365 Retail Markets Automated Refund Exception Flags
Every night, WebRun opens 365 Retail Markets ADM, pulls all refunds and account credits issued that day, compares them to your per-transaction and per-location caps, and posts a flagged exception list to Slack while logging totals to QuickBooks for reconciliation.
How do I automatically flag refund exceptions across all my micro market kiosks?
WebRun pulls every refund and Global Market Account credit issued across all 365 Retail Markets kiosks each night, flags transactions or locations that exceed your configured caps, logs totals to QuickBooks for reconciliation, and posts a refund exception digest to Slack so the finance team can review irregularities before the next trading day.
- Over-cap refunds and credits are caught nightly before they compound into unreconciled losses
- QuickBooks receives a dated refund log per location automatically each night
- Finance teams start the day with a prioritised exception digest instead of a manual ADM export
Built for micro market operators · unattended retail finance teams · operations managers · route supervisors
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
adm.365retailmarkets.comin a real browser with your saved login - no setup, no API keys. -
1
365 Retail Markets - pull all refunds and credits issued today
365retailmarkets.com
WebRun opens 365 Retail Markets to pull all refunds and credits issued today. - Open ADM and navigate to the transaction exception or refund reports
- Pull all refunds and Global Market Account credits issued today across every location
- Flag any single refund above your configured per-transaction cap
- Flag any location where the day's total refund value exceeds its daily refund threshold
- Note the location, time, transaction ID, amount, and item or reason for each flagged refund
Done when All refunds and credits for the day are captured, with flagged exceptions identified by location and amount.
-
2
QuickBooks - log refund totals for reconciliation
- Log the day's total refund amount per location as a liability adjustment in QuickBooks
- Tag each entry with the location name and date for reconciliation against kiosk revenue
Done when QuickBooks has a dated record of refund totals by location ready for monthly reconciliation.
-
3
Slack - post refund exception digest to finance team
slack.com
WebRun opens Slack to post refund exception digest to finance team. - Post a refund exception digest to the finance channel listing flagged transactions with location, amount, and reason
- Sort by exception severity: single over-cap refunds first, then location total exceptions
- Keep the digest internal. No refund notices or credits are issued to customers automatically
Done when Finance team has a refund exception digest in Slack to review at the start of the next day.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it issue any refunds or credits to customers automatically?
No. WebRun only reports on refunds and credits that were already issued in ADM. It does not initiate any new refunds or credits on its own.
How do I set the per-transaction and per-location caps?
You configure the caps when connecting the workflow. For example, flag any single refund over five dollars or any location with more than twenty dollars in daily refunds. You can update the caps at any time without changing the workflow.
Can it catch credit abuse on Global Market Accounts?
Yes. Refunds issued as GMA credits are captured alongside cash refunds, so any pattern of unusually high credit activity at a single location or from a single account is included in the exception digest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.