GUIDE O

​ MNICANAL TRANSACTIONAL PROCESSING 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
   
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

Definition 
This  process  allows  ICOMMKT  to  process  daily  purchase orders generated in POS, offline and online 
stores,  obtaining  more  than  75  indicators  that can be used in dynamic segmentation and automation 
processes. 

 
Formats 
4 plain text files must be generated:  
 
Orders:​ Summary of invoiced purchase orders. Information related to the Purchase Order header. 
OrderDetails:​ Detail of the purchase order lines.  
OrderDetailCategories​:  Relationship  between  categories  and  products  of  the  lines  in  the  purchase 
orders.  
CustomersCustomer​:information. The email field is required in this format. 
The structure of each of the files is described below:  
 
 
   
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

 
   
Name  Descriptio Type  Req  Format  Comment 
n 
OrderNumber  Order  CHAR (50)    (​*)​      
Number   
StoreCode  Store Code  CHAR (30)    (​*)​      
UserId  User ID  CHAR (50)    (​*)​     Customer 

Date  Order Date  DATE  (​*)​   dd / mm /   

yyyy 
TotalItems  Number of  DECIMAL (5.2)  (​*)​      
Items in the 
order  ​  
TotalProducts  Quantity of  DECIMAL (5.2)  (​*)​      
Products 
(different 
items) in the 
order  ​  
    DECIMAL  (​*)​     With taxes 
TotalAmount  Total  (10.2) 
amount of 
the order   
      (​*)​      
ItemsAmount  Total        (Without 
amount of  DECIMAL  taxes) 
the items of  (10.2)   
the order 
DiscountsAmount  Amount of  DECIMAL(10.2 (​*)​      
the  )   
discounts 
applied to 
theorder   
ShippingAmount  shipping  DECIMAL(10.2 (​*)​     Send 0 when 
cost    )    there is no 
TaxAmount  Tax amount  DECIMAL(10.2 (​*)​     All taxes 
of theorder    )   
PromoCodes  Promotion  TEXT      (See 
codes  Particular 
applied    Note 1) 
PreShippingAmount  Total Order  DECIMAL(10.2 (​*)​     Order 
Amount  )    amount 
withoutshipp without 
ing cost  shipping 
cost. A value 
greater than 
zero must 
come (it can 
be 
TotalAmount 
when there 
is no 
discriminatio
n or no 
shipping 
cost) 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

DeliveryType  Shipping        (See 

Type  CHAR (50)    Particular 
(Ex:  Note 1) 
Standard, 
Express)   
           
CHAR (50)   
    SubType of  (See Private 
DeliverySubType  Shipping  Note 1) 
(Ex: Express 
1 day) 
           
DeliveryCompany  Carrier  CHAR (80)   
 
PaymentMethod  Payment         
  Method  CHAR (80)    (See Private 
 
  (Ex: Card,  Note 1) 
 
Cash, 
PayPal) 
 
PaymentMethodDet Payment         
ail  method  CHAR (80)  (See Private 
detail  Note 1) 
(Ex: VISA)   
 

PaymentMethodEnti Payment         
ty  Method  CHAR (80)  (See Private 
Entity  Note 1) 
(Ex: Bank 
XXXX)   
 
PaymentTerms  Payment         
Terms  CHAR (50)  (See Private 
(Ex: 1  Note 1) 
Payment, 3 
Payments) 
 
 
   
 
 
 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

OrderDetails 
 
 
Name  Description  Type  Req  Format  Comment 
 
StoreCode  Store Code    CHAR (30)  (​*)​      
OrderNumbe Order Number    CHAR (50)  (​*)​      
r   
LineNumber  Line Number    INT (11)  (​*)​      
 
 
Quantity  Quantity  DECIMAL  (​*)​      
(5.2) 
 
 
ItemCode  Product Code  CHAR (80)  (​*)​      
 
ItemName  Product Name  CHAR (200)       
Brand  Product Brand  CHAR (200)       

Description  Product  CHAR (200)       

Description 
Price  Product Price  DECIMAL  (​*)​     (​Final unit price of 
(10.2)  the product after 
  discounts​)Tax 
    DECIMAL  (​*)​     (Unit price of 
.NoListPrice  Price List    (10.2)  product list. Send 
 
same value as 
Price when there 
are no discounts or 
differential prices) 
.No Tax 
SellingPrice  Sale Price  DECIMAL(10.2 (​*)​     (Product price 
)  before discounts. 
  Send same value 
as Price when 
there are no 
discounts)Tax 
.NoImageUrl  URL of the main  CHAR (255)       
product image 
DetailUrl  Detail URL  CHAR (255)       
Product 
Seller Seller  Name d the  CHAR (100)       
Product 
 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

OrderDetailCategories 
 
Name  Descripti Type  Req  Format  Comment 
on 
 
StoreCode  Store Code  CHAR (30)  (​*)​      
OrderNumber  Order  CHAR (50)  (​*)​      
Number 
LineNumber  Line  INT (11)  (​*)​      
Number 
Category  Category  CHAR(255)  (​*)​      
ofproduct 
 
Note: When a product is assigned more than one category, one record must be sent for each category with the same StoreCode / 
OrderNumber / LineNumber. 

 
Customers 
 
Name  Descriptio Type  Req  Format  Comment 
n 
 
UserId  User ID  CHAR (50)    (​*)​     Client 
StoreCod Code  CHAR (30)      Report only when a customer has 
 
eStore  different IDs for each Store 
Email  Customer  CHAR     
(300)   
 
Email 
Customer Collection  JSONKey /  Key /  Ex: {​ "Key": "FIRST_NAME", "Value": 
Value  
 
Data  Value in  "Juan"}, ​ {​ "Key": "LAST_NAME", "Value": 
Json  "Sanchez"} 
format 
 
Special Notes 
 
1) When there is more than one data to be reported for the field, they must be sent one after another using 
a separate separator to the general file. For example: PROCOMOCODE1 ## PROMOCODE2 
 
General Note:  
   
1) As a delimiter it is recommended to use "|". 
2) All fields of type DECIMAL must incorporate the period (“.”) As 
a decimal separator. Do not use thousands separator. 
3) In the fields that do not contain information replace by empty 
or zero as appropriate. 
4) Respect in the archives the order of the fields according to the 
design sent. 
5) Send 0 (zero) in all those integer or decimal fields in which it is 
not applicable to send information. 
 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

NomenclatureFiles: 
 
Orders​ICOMMKT_ORDERS_ [ID SINGLE INSTANCE] _​YYYYMMDD 
OrderDetail:​ICOMMKT_ORDERSDETAIL_ [ID SINGLE INSTANCE] _​YYYYMMDD 
OrderDetailCategories:​ICOMMKT_ORDERSDETAILCATEGORIES_ [ID SINGLE INSTANCE] _​YYYYMMDD 
Customers:​ICOMMKT_CUSTOMERS_ [ID SINGLE INSTANCE] _​YYYYMMDD 
 
Note:  [ID SINGLE INSTANCE] It must be an identifier related to the instance, when there are multiple brands / countries / 
business units represented in different instances of our platform. 
Note2: Files must be generated daily, whether or not they contain information. 
  
Transfer 
The  formats  will  be  received  in  an  SFTP  repository.  Said  repository  can  be  owned  by  the  client  or,  if 
required, ICOMMKT may have a space for this information exchange.  

 
 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

KPIs 
Some of the KPI's after processing are available: 
 
ICOMMKT_Fecha_Primera_Compra: ​Date recorded the first purchase 
 
ICOMMKT_Fecha_Ultima_Compra:​ Date recorded last purchase 
 
ICOMMKT_Dias_Primera_Compra:​Days since first purchase 
 
ICOMMKT_Dias_Ultima_Compra: D ​ ays since last purchase 
 
ICOMMKT_Monto_Ultima_Compra: A ​ mount of last purchase 
 
ICOMMKT_Items_30_Dias: ​items purchased in the last 30 days 
 
ICOMMKT_Items_60_Dias: ​items purchased in the last 60 days 
 
ICOMMKT_Items_90_Dias: ​items purchased in the past 90 days 
 
ICOMMKT_Items_180_Dias: ​items purchased in the last 180 days 
 
ICOMMKT_Items_360_Dias: ​items purchased in the last 360 days 
 
ICOMMKT_Items_Total: i​ tems purchased  
 
ICOMMKT_Marcas_30_Dias : M ​ arks bought in the last 30 days 
 
ICOMMKT_Marcas_60_Dias: ​Marks bought in the last 60 days 
 
ICOMMKT_Marcas_90_Dias: ​Marks bought in the last 90 days 
 
ICOMMKT_Marcas_180_Dias: ​Brand s purchased in the last 180 days 
 
ICOMMKT_Marcas_360_Dias: ​Marks purchased in the last 360 days 
 
ICOMMKT_Marcas_Total: M ​ arks purchased 
 
ICOMMKT_Categorias_30_Dias c ​ ategories purchased in the last 30 days 
 
ICOMMKT_Categorias_60_Dias c ​ ategories purchased in the last 60 days 
 
ICOMMKT_Categorias_90_Dias c ​ ategories purchased in the past 90 days 
 
ICOMMKT_Categorias_180_Dias ​categories bought in the last 180 days 
 
ICOMMKT_Categorias_360_Dias: C ​ ategories bought in the last 360 days 
 
ICOMMKT_Categorias_Total: ​Categories bought 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

ICOMMKT_Compras_30_Dias: ​# shopping in the last 30 days 

 
ICOMMKT_Compras_60_Dias: ​# shopping in the last 60 days 
 
ICOMMKT_Compras_90_Dias: ​# shopping in the last 90 days 
 
ICOMMKT_Compras_180_Dias : # ​ of purchases in the last 180 days 
 
ICOMMKT_Compras_360_Dias: ​# of purchases in the last 360 days 
 
ICOMMKT_Compras_Total: # ​ of purchases  
 
ICOMMKT_Valor_30_Dias: ​Amount purchased in the last 30 days 
 
ICOMMKT_Va lor_60_Dias: ​Amount purchased in the last 60 days 
 
ICOMMKT_Valor_90_Dias: ​Amount purchased in the past 90 days 
 
ICOMMKT_Valor_180_Dias: A ​ mount purchased in the last 180 days 
 
ICOMMKT_Valor_360_Dias: A ​ mount purchased in the last 360 days 
 
ICOMMKT_Valor_Total: ​Amount purchased 
 
ICOMMKT_ValorProm_30_Dias: T ​ icket Average last 30 days 
 
ICOMMKT_ValorProm_60_Dias : ​Ticket average in the last 60 days 
 
ICOMMKT_ValorProm_90_Dias: T ​ icket average in the last 90 days 
 
ICOMMKT_ValorProm_180_Dias: ​Ticket average the last 180 days 
 
ICOMMKT_ValorProm_360_Dias: ​Ticket average in the last 360 days 
 
ICOMMKT_ValorProm_Total: ​Ticket average 
 
ICOMMKT_RFM_30_Dias: ​RFM in the last 30 days 
 
ICOMMKT_RFM_60_Dias ​RFM in the last 60 days 
 
ICOMMKT_RFM_90_Dias: ​RFM in the last 90 days 
 
ICOMMKT_RFM_180_Dias: ​RFM in the last 180 days 
 
ICOMMKT_RFM_360_Dias: ​RFM in the last 360 days 
 
ICOMMKT_RFM_Total: R​ FM Total 
 
ICOMMKT_Code: ​codespromotion codes redeemed nes in the last 30 days 
 
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

ICOMMKT_CodeigosPromo_60_Dias: P ​ romotional codes redeemed in the last 60 days 

 
ICOMMKT_CodigosPromo_90_Dias: P ​ romotional codes redeemed in the last 90 days 
 
ICOMMKT_Code  codesPromo_180_Dias:  ​Promotional  codes  redeemed  in  the  last  180in the last 180 
days 
 
daysCodedays_dreams_Combuses c ​ odes in 360days 
 
ICOMMKT_CodigosPromo_360_Total: P ​ romotional codes redeemed in its history 
 
ICOMMKT_Stores_30_Dias: Store ​codes where you bought in the last 30 days 
 
ICOMMKT_ Stores _60_Dias: Store ​codes where you bought in the last 60 days 
 
ICOMMKT_ Stores _90_Dias: s ​ tore codes in the last 90 days where you bought in the last 90 days 
 
ICOMMKT_ Stores _180_Dias: Store c ​ odes where you bought in the last 180 days 
 
ICOMMKT_ Stores _360_Dias: Store c ​ odes where you bought in the last 360 days 
 
ICOMMKT_ Stores _Total: Store ​codes where you bought in your history 
 
ICOMMKT_Methods Last Purchase Payment: P ​ ayment Methods​ o
​ n the last purchase 
 
ICOMMKT_ Last Purchase Shipping: ​MethodsShippingon the last purchase 
 
methodsICOMMKT_ Last Purchase: ​Itemsitems purchased on the last purchase 
 
ICOMMKT_ Last Purchase: B ​ randsMarks bought on the last purchase 
 
ICOMMKT_ Last Purchase: C ​ ategoriesCategories purchased on Last Purchase 
 
ICOMMKT_Best Purchase: S ​ ellersVendor Codes​ i​ n the last purchase 
 
ICOMMKT_Stores of Last Purchase: ​Code of stores in the last purchase  
 
ICOMMKT_ Promo codes of Last Purchase: ​Promotional codes redeemed in the last purchase 
 
 
 
   
 GUIDE O
​ MNICANAL TRANSACTIONAL PROCESSING 

News Omnicanal processOmnichannel 

Incorporation DashboardDashboard  
 
Ahas  been incorporated in the home of the platforms that have omnichanel integration through which 
you can view the information of the sales that are processed daily and perform a macro-level analysis 
of your evolution. 
  
Due  to  the  sensitivity  of  the  data,  the  ROOT  role  and  two  new  profiles  were  assigned  permission  to 
access the Omnicanal Dashboard: 
  
1)  Superadmin:  with  similar  permissions  to  an  Admin,  but  with  the  possibility  of  accessing  this 
Dashboard. 
2) FullCommerce Viewer: with similar permissions to the viewer, but also access to this new screen.