CEGID Guide
This article describes briefly some of the features supported by this system and how to manage them.
Introduction
CEGID is a retail POS system that supports the collection of Order data and the Management of products.
Stock Buffering
When product and inventory requests are imported by the CEGID integration, Aurora pre-processes the requests and applies stock buffers according to values stored at Store, Product, and Variation level.
The order of precedence, when buffering a stock value, is as follows:
- Variation Level
- Product Level
- Store Level
Where a zero or positive integer value is defined, the value will be used, otherwise the next value in the order of precedence will be used i.e.
- First, the product variation (SKU level) is checked for a CEGID Stock Buffer variation field value.
- Second, the product is checked for a CEGID Stock Buffer product field value.
- Third, the CEGID integration settings are checked for a store level Stock Buffer value.
If any of these values are zero or a positive integer, the value will be used as the stock buffer for the respective stock value within the request and no further values are checked.
Product and Variation level values are defined using a CEGID Stock Buffer field. Please see Product Fields and Product Attributes and Variations for more details about editing field values.
The Store level value can be edited within the CEGID integration settings and Stock.
Logging
The requests received from and send to the CEGID system can be logged for debugging purposes if desired using the "Log Requests?" option in the Aurora Back-end under Store > Settings > Feeds > CEGID.
When this is active, all requests and responses for the CEGID system will be logged to the API Integration Log found in the Aurora Back-end under Store > Logs > API Integration Log.
Types of Log Entries (Modified vs. Unmodified)
The CEGID API Log entries include two separate log entries, as follows:
- Unmodified requests (received from CEGID) and responses (send to CEGID), e.g. "Order Export".
- Modified requests (processed by Aurora for consumption but the Aurora API) and responses (processed by Aurora for consumption but CEGID), e.g. "FTP Delivery: Order Export"
The unmodified entries are the raw files receive from CEGID or generated by the Aurora API.
The modified entries are the files that are actually processed by the Aurora API or received by CEGID after Aurora has finished applying its automated schema changes.
The following is an example of a pair of entries from an Order Export from Aurora to CEGID.

Updated over 2 years ago