Glossary¶
Terminology and abbreviations used within Zwerfkei. When in doubt about a term used elsewhere in this documentation, check here first.
| Term | Abbreviation | Description |
|---|---|---|
| Master Data | - | Catalogue data (categories, attributes, product/variant content, images) is mastered in PIM (Ergonode). Transactional data (stock, prices, orders) remains mastered in BC/NAV. See Ergonode. |
| Microsoft Dynamics 365 Business Central | BC | The ERP system used by Zwerfkei. See Microsoft Dynamics Business Central. |
| Microsoft Dynamics NAV | NAV | The legacy predecessor of Business Central (formerly known as "Navision", now an outdated term), still in use by Zwerfkei Backoffice (legacy). See Legacy Integration. |
| Product Information Management | PIM | Refers to Ergonode, the PIM system used by Zwerfkei. See Ergonode. |
| Zwerfkei API | - | The new backend (Laravel): business logic, domain APIs and all external integrations behind the Zwerfkei Website. A technical layer with no user interface. Previously referred to internally as "Zwerfkei Backend". See Overview. |
| Zwerfkei Backoffice (legacy) | - | The legacy monolithic application (CodeIgniter) predating the new platform. Still used by employees for day-to-day operations during the migration; no new development takes place here. Previously referred to internally as "Zwerfkei Old" / "Zwerfkei Backend OUD". See Architecture. |
| Zwerfkei Medewerkersportaal | - | The internal portal for store employees — printing tickets, tracking repairs, generating QR codes, and other in-store operations. Previously referred to internally as "Zwerfkei Backend V2". Not yet documented in detail. See Overview. |
Adding a term
Found a term or abbreviation used elsewhere in this documentation without an explanation? Add it here in alphabetical order within its category.