Skip to main content
When referring to “incoming” and “outgoing” data, ONELOX’ point of view is used as a reference
ONELOX requires a separate directory for each resource type.
For incoming data, a nested archive directory is used to move processed files into. ONELOX does not require outgoing files that have been processed by the external system to be moved or deleted.
Every time ONELOX transfers data, a unique filename is generated so files will never be overwritten accidentally.

​
Example structures

​
Using ONELOX as the only fulfillment system

Incoming and outgoing data as seen from ONELOX’ point of view 
- /onelox
    - /data
        - /in
            - /delivery_notes
                - /archive
            - /products
                - /archive
        - /out
            - /inventory
            - /shipments

​
Using ONELOX alongside other fulfillment systems

Incoming and outgoing data as seen from the source system’s point of view 
- /data
    - /out
        - /onelox
            - /delivery_notes
                - /archive
            - /products
                - /archive
    - /in
        - /onelox
            - /inventory
            - /shipments