API, EDI, E-mail, FTP order methods for GSOR (first party) vendors.


API


Application Programming Interface (API) 


Groupon Specs 


Overview: 

With this option, you will make a call to Groupon’s API endpoint for orders and shipping tracking. Marking orders exported in CI is required - you must call this export endpoint immediately after the get_orders endpoint. If not exported, this could lead to CS cancellations and loss of payment for shipped orders that remain unexported in CI.


EDI 


Electronic Data Interchange (EDI) 


Groupon EDI Specs


Overview: 

With EDI, a VAN is required in order to interchange data. You will be able to receive order, reject and/or accept orders, add shipping tracking, and update inventory to SKU’s. Groupon only supports the 850, 855, 856, 824, and 846. Currently, this is the only automated option we offer for inventory updates. This option is only available to USA region and you have to be operating in Gateway. Orders will be marked as exported in CI upon Groupon’s send of the order via the 850.


FTP


File Transfer Protocol (FTP)


Groupon FTP Specs


Overview: 

The CommerceInterface (CI) FTP method allows vendors to interact with the CI platform via FTP file transfers for orders and shipping tracking. Orders will be marked as exported in CI upon Groupon’s FTP file drop.


E-mail 


Overview:

With the e-mail order method option, e-mail notifications are sent to assigned users every time new orders are dropped in Commerce Interface at the vendor established frequency in CI (every 1 hour up to 4 hours). This option works within CI and does not support inventory updates via CI. Orders will be marked as exported in CI upon email notification.




Order Method

Time of 'Export' Action in CI

Export Frequency

API

Order send via API call

Managed by vendor

EDI

Order send via Groupon

Managed by Groupon - every 10-15 minutes

FTP

Order send via Groupon

Managed by Groupon - every 10-15 minutes

Email

Order send via email

Managed by vendor - can set up to 4hr delay in CI