Skip to navigation

52ViKING help center

Concepts, configuration, and day-to-day tasks for the POS.

View as Markdown

Examples, step-by-step procedures, useful tips, and background on how 52ViKING works — for shop assistants at the till, for managers configuring a store, and for developers who need to know what the API field names actually mean.

If you are integrating, the fastest route in is usually Platform concepts for the model, then Store Management for how each entity is configured.

Browse by section

SectionTopicsCovers
Platform concepts12Discount types, payment methods, self-scanning, credit sales, returns, balance and bookkeeping
Store Management39The full configuration surface: articles, campaigns, discount groups, operators, tills, reports, stock
ViKING POS14The staffed till: sales, returns, till management, customers, campaigns, SCO, monitoring
ViKING MPOS6Mobile POS on Android, deployment via MDM
Emergency POS4Setup, activation, and recovery
POS Designer9Diagrams, layouts, components, resources
Unified commerce2Cross-channel commerce and the cloud APIs
52LEASING1Danish-only; see the note on that page
52eSELLER1The e-commerce suite
About this help4Using the help, contact, trademarks

Recently added and updated topics are in What’s new.

Concepts developers ask about most

Configuring promotions through Master Data takes two things at once: the endpoint schema, and the topic explaining what a discount group’s Buy side actually is.

Discount groups

What the rule looks like in Store Management.

Buy side / Get side

Which articles trigger, which receive.

Discount types

Mix, amount, ladder, percent-of-cheapest.