Akinon orders

On a store that runs on Akinon, no code needs to be written to get orders to Sayproof. Sayproof connects to Omnitron with an Omnitron user you create and reads new or changed orders itself at regular intervals (every 15 minutes by default). The orders read are recorded in the same way as orders sent by your store system; the right to write a review and the invitations follow the same rules.

When to use it

• If your store runs on Akinon (Omnitron), set up the connection on this page.
• If your system has no ready connection, your store system sends the orders: Sending orders and deliveries.

In the panel the two ways are shown one under the other on the Integration › Order transfer tab: Read from your platform and Sent by your store.

What you need

Item	Description
Omnitron address	The address you use to open Omnitron, for example https://omnitron.yourbrand.com. Only the domain is used; a path written after it is dropped. An address with user details, a query string or # is not accepted.
Omnitron username and password	A separate user created for this job that can only see orders. Do not use your own administrator account; you can switch the separate user off whenever you like.
Omnitron channel number	The Omnitron number of the sales channel to read orders from; digits only. Your Akinon team can tell you if you do not know it.
Sayproof channel	The channel the orders read are written to. The order’s market is this channel’s market.

A Sayproof channel can have one connection per platform.

Setting up in the panel

1. On the Integration › Order transfer tab, press Set up a connection in the Read from your platform section.
2. In the Where to read from step, choose Akinon (Omnitron) as the platform and the Sayproof channel.
3. In the Connection details step, fill in Omnitron address, Omnitron channel number, Omnitron username and Omnitron password. How many days to read back the first time takes a value between 1 and 365; the default is 30 days.
4. In the Try it step, press Try the connection. Sayproof connects to Omnitron and reads the first page (at most 100 orders) of the orders within the chosen number of days. The result shows the number of orders read, the orders that could not be read and at most five sample orders: Order no., Order date, Payment, Products, Shipping status, Has email. The customer’s email address is not shown. Nothing is saved in this step.
5. Save and start reading only becomes available after a successful try. If any detail changes after the try, the connection has to be tried again.

After saving, the connection appears on the Platform connections card. The card shows Read frequency, Last read, In the last read (orders read and how many were new), Could not be read and Last error. Buttons:

Button	Purpose
Read now	Starts a read without waiting for the next one. It is unavailable while the connection is paused or the channel is off.
Try the connection	Repeats the try with the saved details; saves nothing.
Pause / Resume	Stops reading or starts it again.
Edit the connection	Changes the Omnitron address, the Omnitron channel number and the Read frequency (between 5 and 1440 minutes). Reading continues where it left off; orders already transferred are not read again. If the address points to another server, the Omnitron username and Omnitron password are entered again in the same form; the saved sign-in details are not sent to the new address (400 invalid / address_needs_credentials). The Sayproof channel does not change in this form.
Change the sign-in details	Saves the new password; if the username is left empty, the current username is kept.
Remove the connection	Stops reading. Orders already read and invitations already sent are not deleted.

Reading

• A read runs every 15 minutes by default; the frequency can be changed to between 5 and 1440 minutes with Edit the connection. The first read takes the orders whose change time falls within the chosen number of days.
• Later reads take the orders changed since 10 minutes before the previous read started. Reading the same order again is safe: the order is updated and no duplicate is created.
• Only one read runs at a time for a connection.
• A read takes at most 50 pages (100 orders per page). If the limit is reached before the orders run out, the card shows “The last read hit the page limit” and the next read continues from the change time of the last order read (with a 10-minute margin).
• If a read fails, its position does not move; the next read tries the same range again after the read interval and the reason appears on the Last error line. The moment a read starts is recorded at once; while a read is running, no second read starts for the same connection.

Sayproof first signs in to Omnitron:

POST https://omnitron.yourbrand.com/api/v1/auth/login/
Content-Type: application/json

{"username": "sayproof-reader", "password": "<password>"}

The key field of the answer is used as the token, and the order list is read sorted by change time:

GET https://omnitron.yourbrand.com/api/v1/orders/?channel=3&modified_date__gte=2026-09-02T12:00:00%2B00:00&ordering=modified_date&limit=100
Authorization: Token <token>

• Orders are read from the results list of the answer. Further pages are reached by following the next address; that address must be on the same domain as the Omnitron address.
• If the token has expired (401), Sayproof signs in again once.
• Each request times out after 30 seconds and an answer may be at most 20 MB.

Fields read

Each row lists the fields checked in order; the first one with a value is used.

Information in Sayproof	Field read in Omnitron
Order number	number
Order status	status.value, status
Order date	date_placed, created_date
Change time	modified_date
Customer email	customer.email, email, shipping_address.email, billing_address.email
Customer phone	customer.phone_number, shipping_address.phone_number, billing_address.phone_number
Customer identifier	customer.id, customer
Language	language_code (first part only; tr-tr → tr)
Product lines	orderitem_set, items
Line identifier	id, pk on the line
Product code	product.sku, sku
Group code	product.base_code, base_code
Product name	product.name, name
Quantity	quantity
Line status	status.value, status on the line; the order status when empty

• The customer email does the same job as the customer_email field in the order data sent by a store system: the invitation is sent to this address and the order is verified with it.
• The customer phone does the same job as the customer_phone field in the order data: the number is for invitations on WhatsApp. Until invitations by WhatsApp arrive with v2, the phone number is not stored.
• The product code must match the product key in your product source and the code given to the container on the product page.
• The order’s address, price and payment details are not stored in Sayproof.

Status mapping

Omnitron status codes are mapped to Sayproof’s payment and shipping statuses according to the table below. The table also appears in the How statuses are matched section of the connection card in the panel.

Omnitron code	Meaning in Omnitron	Payment	Shipping status
50	Cancellation requested	Paid	Placed
100	Cancelled	Voided	Cancelled
200	Waiting	Payment pending	Placed
300	Waiting for payment	Payment pending	Placed
350	Waiting for approval	Payment pending	Placed
400	Approved	Paid	Placed
450	Preparing	Paid	Preparing
500	Shipped	Paid	Shipped
510	Shipped, customer informed	Paid	Shipped
520	Ready for pickup in store	Paid	In transit
540	Delivery attempted	Paid	In transit
550	Delivered	Paid	Delivered
600	Returned	Refunded	Returned

• The delivery date is the line’s modified_date, or the order’s modified_date if the line has none.
• For invitations and the right to write a review, the line must be Delivered and the order Paid. The invitation is sent once the waiting time on the Invitation sending screen has passed.
• If a code that is not in the table arrives, the order or line is not read and is counted on the Could not be read line.

Orders that could not be read

In the panel	Reason
number or date missing	The order has no number, no order date or no list of product lines
status not recognised	If the order’s status is not in the table the order is skipped; if a line’s status is not, only that line is skipped
product code missing on a line	The line has no line identifier or no product code; the line is skipped
no readable product lines	None of the order’s lines could be read
could not be saved in Sayproof	The order was read but could not be saved in Sayproof (for example, there is no rule for the channel’s market)

Orders that could not be read or saved do not stop the read; the other orders are saved. If none of the orders read can be saved, the read counts as failed and its position does not move; the reason appears on the Last error line.

Failures

When a read or a try fails, the panel shows one of these reasons:

In the panel	Meaning
a username and password are needed	The connection has no saved username or password
the username or password was not accepted	Omnitron refused the sign-in or the answer has no token
the domain could not be reached	The Omnitron address could not be resolved
the address is not reachable from the internet	The address leads to a private network address; such addresses are not contacted
couldn’t connect to the server, a secure connection could not be made	The connection or the TLS handshake failed
the source did not answer in time	The request got no answer within 30 seconds
the address redirects elsewhere; enter the direct address	Omnitron returned a redirect; redirects are not followed
the other system returned an error, status code	Omnitron answered with something other than 200 (for example http_status: 403)
the platform’s answer could not be read, the platform’s answer is too large	The answer is not JSON or is larger than 20 MB
the platform pointed to another address for the next page	The next address is not on the same domain as the Omnitron address
the stored sign-in details couldn’t be read; enter them again	The saved password could not be decrypted; enter it again with Change the sign-in details
the read stopped with an unexpected error	An unexpected error occurred; the read is tried again after the read interval

Security

• The password is stored encrypted and never shown again in the panel or in API answers.
• Only https addresses are contacted; private network addresses and redirects are refused.
• Connections are only seen and managed by a user signed in to the panel with the “Can change settings” permission; these actions cannot be taken with an API key.
• Setting up, changing, trying, reading manually and removing are recorded on the Activity history screen. A change of sign-in details only appears as a “Sign-in details renewed” line; the values are not recorded. The removal entry names the removed connection’s platform and channel.