MNG Seller Pays Shipment Extension
Extension Installation
Preliminary Works
The following information is requested from the provider for the brand-specific and production (live) environment.
API_URL
IBM_CLIENT_ID
IBM_CLIENT_SECRET
PAYMENT_TYPE
SHIPMENT_ARRIVE_TO_BRANCH_MESSAGE
SHIPMENT_PREPARED_MESSAGE
SHIPMENT_DELIVERED_MESSAGE
DELIVERY_TYPE
CUSTOMER_NUMBER
PASSWORD
PACKAGING_TYPE
COMPANY_EMAIL
A secret_key is generated with a minimum length of 41 characters. The generated key must be kept throughout the installation. An example command line to generate a random key:
openssl rand -base64 41
An address ID must be set for the default destination or origin information. It can be created using the extension's address creation method (example curl is given below). Ensure that the address ID is accurately configured to facilitate the smooth handling of return shipments within the Omnitron configuration.
curl --location --request POST '{extension_url}/addresses' \
--header 'x-akinon-request-id: {guid}' \
--header 'x-akinon-api-version: 1.0' \
--header 'Authorization: Basic {token}' \
--header 'Content-Type: application/json' \
--data-raw '{
"id": "1234", // return_destination_extension_id in Omnitron config,
"addressName": "Test Address Name",
"addressDescription": "Test Description",
"phone": "+971547932376",
"email": "testuser@example.net",
"type": "DISTRIBUTION_POINT",
"address": {
"country": {
"id": 1, // optional
"code": "TR",
"name": "TR"
},
"city": {
"id": 1, // optional
"name": "Antalya"
},
"township": {
"id": 1, // optional
"name": "Konyaaltı"
},
"district": {
"id": 1, // optional
"name": "Hurma Mahallesi"
},
"zipcode": "33004",
"addressLine": "Antalya Konyaaltı Mahallesi 229. Sokak No.4 Daire 5"
}
}'
Environment Variables
The extension installed to the relevant project in ACC must have the following environment variables. Environment variables can be entered before or after the deployment phase. As changes are made to the environment variables, the deployment process must be performed again.
Extension-specific
API_URL
URL received during the preliminary works phase (without a trailing slash at the end)
IBM_CLIENT_ID
IBM_CLIENT_ID received during the preliminary works phase
IBM_CLIENT_SECRET
IBM_CLIENT_SECRET received during the preliminary works phase
PAYMENT_TYPE
PAYMENT_TYPE received during the preliminary works phase
SHIPMENT_ARRIVE_TO_BRANCH_MESSAGE
SHIPMENT_ARRIVE_TO_BRANCH_MESSAGE received during the preliminary works phase
SHIPMENT_PREPARED_MESSAGE
SHIPMENT_PREPARED_MESSAGE received during the preliminary works phase
DELIVERY_TYPE
DELIVERY_TYPE received during the preliminary works phase
CUSTOMER_NUMBER
CUSTOMER_NUMBER received during the preliminary works phase
PASSWORD
PASSWORD received during the preliminary works phase
PACKAGING_TYPE
PACKAGING_TYPE received during the preliminary works phase
COMPANY_EMAIL
Company’s email address
Generic
SECRET_KEY
The generated secret key during the preliminary works phase
ADMIN_EMAIL
The e-mail address of the installer can be entered
ADMIN_PASSWORD
A newly created and extension-specific strong password
ADMIN_USERNAME
A username can be entered (example: ‘akinon’)
Omnitron Settings
MNG Satıcı Öder can be selected as the Shipment Provider in Omnitron to integrate with the extension installed. Additionally, an easy return option can be defined to enable easy return methods. Explanations on how these settings can be configured are detailed in the sections below. Please note that these two operations are independent and optional.
Shipping Provider
To add MNG Satıcı Öder, a new shipping provider is added to SHIPPING_PROVIDERS in Dynamic Settings through Omnitron.
Example Omnitron Configuration:
Klass
ExtensionShippingProvider Class
Urls Code
{ "urls": { "base_url": "{SHIPMENT_EXTENSION_URL}
", } }
Serializers
Order Serializer: ExtensionShippingOrderSerializer Class Response Serializer: ExtensionShippingResponseSerializer Class
Configurations Code
{ "strategies": { "query_type": "SHIPMENT_ID", "generate_shipment_origin_strategy": "<addressId>", "generate_shipment_product_strategy": true, }, "pay_on_delivery_option": false, "delivery_type": "CUSTOMER", "auth": { "username": "{SHIPMENT_EXTENSION_ADMIN_USERNAME}", "password": "{SHIPMENT_EXTENSION_ADMIN_PASSWORD}" }, "is_active": { "query": true, "send_shipping_info": true, "delete_shipping_info": true, "query_by_order": true }, }
Easy Return Shipping Option
One easy return shipping option must be defined in Omnitron to be specific for the extension installed. Explanations on how the settings should be made at this stage are in the section below.
Example Omnitron Configuration:
Shipping Company
Extension Cargo
Shipping Company Auth Code
{ "url": "{SHIPMENT_EXTENSION_URL}
", "username": "{SHIPMENT_EXTENSION_ADMIN_USERNAME}
", "password": "{SHIPMENT_EXTENSION_ADMIN_PASSWORD}
", “send_user_address”: True, "return_destination_extension_id":"{address_id}
" }
Start Date Gap
This variable is used to delay the start date for using the return code. If this value is set to 0, the customer can request a refund on the same day.
Delivery Time
The delivery_time variable indicates the duration for which the return code will be valid and usable. If the product is not shipped by the customer within this period, the code becomes invalid.
Shipping Company Prefix
If a prefix is to be added to the return code, this field should contain the short name of the brand. This short name can be any value determined by the brand.
Shipping Company Rules
{ "product": { "field_key": "attributes__easy_return_method", "field_values": [ [ "", null ] ] } }
Status
active
Last updated
Was this helpful?