User Help
How to use this screen/report.
Intended for all users
User Roadmap
Quick support tips.
Intended for in store support use
Technical Roadmap
Technical support tips.
Intended for support staff
User Guides
Concepts, What's possible, overviews
Intended for all users
Technical & API
How to customise, how it logically works
Intended for all advanced users and IT staff
Deep Internals
Deeper explanations on various subsystems
Intended for advanced use and interface developers
Design Notes
How and why it works.
Intended for advanced support staff
Source Code
Access to developers only
Design Notes
Design notes provide a range of extremely low level technical insights into how various parts of the Fieldpine system are built. They are intended for advanced support staff or developers. Using design notes you can quickly get up to speed on how various parts of the system work, or what underlying options are present for different screens.
- Design notes are provided on an as-is where-is basis.
- Fieldpine Support are unable to help with questions on design notes.
- You should not rely on information in design notes to build or extend the system.
- Anything in a design note is fluid and can be changed without warning.
- Design notes may not include all information, and may in some cases refer to source code.
By Screen
This section lists how individual screens operate
Discount SelectPOS Command Processing
This section lists how individual POS-Commands operate internally
Discount() system(quickc...)Retail Logic Processing
This section lists functions performed by Retail Logic which are typically business wide and common operations such as edit products, send Purchase Order
eCommerce Interface Memberships Supplier InventoryBackground Processing
This section lists internal components and how they work
SyncHidden PeerMesh Mesh Memory (lane) MultiRetailer PriceBands One Off Specials Config Policies Cameras LockRulesHistoric/Retiring
Components that are being retired or replaced
AutoMaintainance