Basic Setup

Overview

After the Akinon OMS application is deployed to a customer's ACC Project, the OMS menu becomes available in Omnitron's left navigation. Before using the system, initial configurations must be completed via Akinon OMS > Settings > Basic Setup. This section enables fundamental setup operations that are critical for syncing data from Omnitron and verifying system integrity.

Before starting the Basic Setup, ensure that the following configurations are completed in Omnitron:

• Sales Channels

• Addresses

• Locations

Once these elements are set, you can proceed with the Basic Setup steps in OMS.

Sales Channels

The "Sales Channels" step integrates the various channels through which sales are conducted into the OMS. Organizations operating on multiple platforms or sales channels can utilize this setting. The Sales Channel setting is necessary for businesses that sell their products both through their own website channel and via marketplaces.

Purpose of using the Sales Channels step:

1. Omnitron Integration: Sales Channels defined and configured in Omnitron are transferred to Akinon OMS. This ensures consistency and synchronization.

2. Unified Product and Sales Management: By integrating sales channels into Akinon OMS, businesses can monitor and manage orders originating from various channels (such as online stores, marketplaces, physical retail stores) in a unified manner within the OMS.

Running the Installation Step:

Navigate to the Sales Channels section under the Basic Setup menu in OMS and click the RUN INSTALLATION STEP button. This action imports all Sales Channels from Omnitron into Akinon OMS, enabling these channels to be used and assigned within OMS configurations such as locations and scenarios.

Different Sales Channels may have unique requirements or processes for order processing. Akinon OMS allows for customization and specific configurations for each Sales Channel.

If new Sales Channels are created in Omnitron after the initial setup, the Sales Channels installation step in Akinon OMS needs to be run again to import these new channels.

In the Sales Channels settings, a "Requirements" check is performed. If a sales channel has been added or updated in Omnitron, this field will display True. When all Sales Channels are identical in both OMS and Omnitron, it will show as False.

Additionally, on the Setup Channels form, channels are transferred to OMS via tasks. To monitor the execution status of these tasks, there is a "Status" field. You can check if the tasks are running by using the Update Status button.

After clicking the Update Status button, the status field will display one of the following options:

• READY: The task is prepared and ready to run.

• WORKING: The task is currently in progress.

• FINISHED: The task has been completed successfully.

• FAILED: An error occurred while the task was running.

Address

With the "Address" step, the address details added to the Address Mapping section of Omnitron, which relate to store locations, distribution centers, or warehouses, are transferred to the OMS.

This address information is used in fulfillment processes such as determining the nearest stock location for order shipment, calculating shipping costs, and calculating delivery routes.

After the initial setup, when new address information is added to Omnitron, you need to navigate to OMS > Settings > Basic Setup > Address and run the "RUN INSTALLATION STEP" again to ensure that the new addresses are imported and updated.

In the Address settings, a "Requirements" check is performed. If an address has been added or updated in Omnitron, this field will display True. When all Addresses are identical in both OMS and Omnitron, it will show as False.

Additionally, on the Setup Addresses form, addresses are transferred to OMS via tasks. To monitor the execution status of these tasks, there is a "Status" field. You can check if the tasks are running by using the Update Status button.

After clicking the Update Status button, the status field will display one of the following options:

• READY: The task is prepared and ready to run.

• WORKING: The task is currently in progress.

• FINISHED: The task has been completed successfully.

• FAILED: An error occurred while the task was running.

Retail Store

The "Retail Stores" step enables the copying of store details from Omnitron's Sales Channels > Store Management > Retail Stores to the OMS. This is applicable to businesses with physical retail stores.

This step transfers pre-defined store records from Omnitron to Akinon OMS. It ensures that all retail stores defined in Omnitron are available and correctly set up in Akinon OMS for order management.

If a store or warehouse has not been previously defined in Omnitron, or if it will be defined later, this step can be skipped initially or completed again after updates.

To run the Retail Stores setup step, click the RUN INSTALLATION STEP button in OMS > Settings > Basic Setup > Retail Stores.

Within the Retail Stores configuration, a "Requirements" verification is conducted. This field will indicate True if any store details have been newly added or modified within Omnitron. If the data is consistent between OMS and Omnitron, it will show False.

Furthermore, the transfer of retail store information to OMS is managed through tasks accessible in the Setup Retail Stores form. The "Status" field provides insight into the current processing state of these tasks. To refresh this status and ascertain whether the tasks are actively running, click the Update Status button.

Following an "Update Status" action, the status field will reflect one of the following states:

• READY: The task is queued and awaiting execution.

• WORKING: The task is currently being processed.

• FINISHED: The task has been executed without any issues.

• FAILED: The task encountered an error during its operation.

Webhooks

Webhooks are used to trigger tasks and update data in response to specific events within the system, such as when a product is packaged, an order is shipped, or packages are delivered. They help route data updates efficiently during fulfillment processes, ensuring efficient communication of updates and changes.

Webhook event details can be copied to OMS by running the Webhooks setup step in Basic Setup. To run the Webhooks setup step, navigate to OMS > Settings > Basic Setup > Webhooks and click the RUN INSTALLATION STEP button.

Additionally, Webhooks are defined on the OMS > Settings > Webhooks page.

In the Webhooks configuration, a "Requirements" assessment is performed. This field will show True if any Webhook subscriptions have been newly added or updated within Omnitron. If the webhook configurations are identical between OMS and Omnitron, the field will display False.

Additionally, the synchronization of Webhook details to OMS is handled via tasks available in the Setup Webhooks form. The "Status" field provides a real-time overview of these tasks' progression. To refresh this status and determine if the tasks are currently executing, click the Update Status button.

After an "Update Status" action, the status field will indicate one of the following states:

• READY: The task is initialized and awaiting processing.

• WORKING: The task is actively being synchronized.

• FINISHED: The webhook data has been successfully transferred.

• FAILED: An error occurred during the webhook synchronization process.

Stock Integration

Akinon Order Management System (OMS) Stock Integration is used to manage and synchronize stock levels across various sales channels and locations. Effective and efficient inventory management is essential, and Stock Integration facilitates optimal fulfillment and overall inventory control by ensuring accurate tracking and synchronization of stock levels across different locations.

OMS maintains up-to-date stock levels by synchronizing data from different stock locations, such as warehouses and retail stores. This synchronization ensures that the stock information within the OMS reflects the actual available inventory.

During the order planning process, Akinon OMS utilizes Stock Integration to determine product availability. It aids in deciding which location will fulfill an order based on current stock levels, ensuring efficient order processing and minimizing delays caused by out-of-stock issues.

Businesses often operate with multiple stock locations, including warehouses and retail stores. Stock Integration enables the OMS to manage inventory across all these locations, providing a comprehensive view of stock availability.

The OMS can integrate with the customer's existing stock management systems. This integration ensures seamless communication between systems, allowing any changes in stock levels within the customer's system to be accurately reflected in the OMS.

Stock Integration in OMS also supports stock reservations for orders. This feature is particularly useful for items that have not yet been transferred to the ERP system or moved to a 'Preparing' status. It ensures that inventory is set aside to fulfill specific orders, thereby preventing overselling.

For customers who only use their stores for package distribution and their warehouses as stock locations, Akinon OMS can be set up with the Zero Stock Engine. This setting assigns product stock quantities of zero to the connected locations. However, if actual stock quantities are required for the locations, the appropriate Stock Engine can be configured with the correct data.

Stock Integration aids in accurate inventory management by providing real-time stock level updates, reducing the risks of stockouts and overstocking, thereby ensuring optimized stock levels.

Accessing Stock Integration Information:

Stock Integration information can be accessed from two pages:

• Akinon OMS > Settings > Basic Setup > Stock Integration

• Akinon OMS > Settings > Product Stock Integration > Stock Location Engine

This setup adds the service from which stock information will be queried when a package is created. The following fields need to be filled in for Stock Integration:

• Requirement: Checks if this task needs to be run. It will appear as true if there are updated stock integration settings in Omnitron, and false otherwise.

• Service Type: Select the stock location service to be used.

• Name: Enter the name of the stock location.

• API URL: Fill in the API URL information for the stock service.

• Authentication Type: Select the authentication method for the stock service.

  • Anonymous request service: No authentication information is required.

  • Basic authentication request service: Username and password information must be entered.

  • Token Authentication Request Service: In addition to the username and password, the Authentication URL field must also be filled in.

Cargo Integration

Cargo Integration is utilized in the management and execution of shipping and logistics operations.

Cargo Integration enables the OMS to connect with various shipping carriers to manage the logistics of order delivery. This integration is crucial for automating the shipping process, tracking shipments, and updating order statuses based on delivery progress.

By integrating cargo services, the OMS can automate the selection of appropriate shipping companies based on predefined criteria such as shipping cost, delivery speed, or geographical coverage.

The setup of Cargo Integration involves defining the shipping integrations that Akinon OMS will use during the order planning process. This is done under the Basic Setup process in Akinon OMS.

To configure Cargo Integration, users need to enter specific details such as the Shipping Name, ERP Code, Shipping Management preferences, Demo and Extension Client preferences, and Shipping Company selection. This data ensures that Akinon OMS identifies and uses the correct shipping services for fulfillment.

In this section, the following cargo company information is added to complete the cargo integration:

• Shipping Name: The name of the cargo company to be used.

• ERP Code: The ERP code associated with the cargo company.

• Shipping Management: Select whether the shipping process will be managed by the OMS. When the cargo processes are managed by the OMS, the necessary fields will vary depending on the selected cargo company. These fields are found in the integration documentation provided by the cargo company and are added as fields to this section based on the cargo company's requirements. If no additional fields appear after selecting a cargo company, it means there’s no predefined integration for that cargo.

• Demo Client: Specify whether cargo processes will be managed by a demo client. The status transitions that will affect the shipment after the Preparing status are determined according to the selected demo client. Previously defined demo clients in OMS are selected from the opened class section. Additionally, the desired Shipping Company is also selected from this section. The selected cargo company will now determine the cargo status transitions and cargo label sending stages. No integration is required, OMS default shipment clients are used.

• Extension Client: The shipping process is managed by the OMS but through a third-party application. Any cargo company can be used as an extension. A cargo company must first be added as an extension. The requirements for adding an extension are determined during the setup process.

• Shipping Company: Select one of the shipping companies that has been added previously.

Akinon OMS supports integration with multiple cargo companies, allowing businesses to select different carriers for various shipment types or regions.

Once cargo integrations are configured, OMS can automatically assign carriers to orders based on the established rules and preferences, streamlining the shipping process.

Cargo Integration can be added and configured on two pages:

• Akinon OMS > Settings > Basic Setup > Cargo Integration

• Akinon OMS > Settings > Shipping Management

To configure Cargo Integration, enter the Shipping Name and ERP Code, and select the Shipping Management and Carrier Company.

Stock Location Sender Address

This step is used to send location addresses from OMS to cargo applications. If a new cargo application is installed or there are any updates to location addresses, running this step ensures that the location addresses are transmitted to and updated within the cargo application.

If your operations rely solely on sales channels rather than distinct marketplace integrations, you can run the Stock Location Sender Address process directly from the Basic Setup to transfer location addresses to the Cargo application.

During this step, the OriginID—retrieved from the sales channel—is required in the Stock Location Sender Addresses form. This ID is automatically added when the sender address task is executed, matching the corresponding location and the cargo company’s address ID within the extension. Alternatively, you can manually input the OriginID in the "Stock Location Sender Addresses OriginID" field located under OMS > OMS Settings.

For the Sales Channel, the Stock Location Sender Addresses in Akinon OMS > Settings must be configured first.

The Stock Location Sender Address settings feature a "Requirements" indicator. This will show True if there are new or modified stock location sender address details concerning your Omnitron Sales Channels that need to be synchronized. If the information is up-to-date between OMS and Omnitron, it will display False.

The actual transfer of these stock location sender addresses to your connected shipping applications is handled by tasks, which you can view in the Setup Stock Location Sender Address form. The "Status" field provides real-time feedback on the progress of these synchronization tasks. To get the latest status and see if the tasks are currently running, click the Update Status button.

The "Status" field will then update to one of the following:

• READY: The system is prepared to send the stock location sender address data.

• WORKING: The data transfer to the shipping applications is currently in progress.

• FINISHED: The stock location sender addresses have been successfully transmitted.

• FAILED: An error occurred during the process of sending the stock location sender addresses.