Magento 2.0 (Adobe Commerce) customers, sales, and refunds

Magento 2.0 (Adobe Commerce) customers, sales, and refunds

Once your Magento 2.0 (Adobe Commerce) integration is connected, Cin7 Core can download customers and orders from Magento, push fulfillment updates back to Magento, and capture refunds.

You can also manage your Magento product catalog and configure Magento settings including payment account mapping, tax rules, and order capture behavior.

Before you start

Download customers

To download customers from Magento to Cin7 Core, go to the Catalog tab and select Download and then Customers. Catalog tab with the Download menu open and Customers selected

This function downloads all customers from Magento to Cin7 Core. If the customer already exists in Cin7 Core, this function updates any details that have been changed in Magento. As Cin7 Core automatically creates customers when processing sales orders (if No consolidation is selected), this function is generally only used for testing purposes.

This function creates a customer in Cin7 Core with contact, billing, and business addresses captured from Magento. You can't upload customers from Cin7 Core to Magento.

Customer field mapping

Cin7 Core

Magento 2

Email

Email

BillingAddress

Addresses (DefaultBilling) country_id, region.region, BillingAddressLine1, Street, Postcode, City

ShippingAddress

Addresses (DefaultShipping) country_id, region.region, BillingAddressLine1, Street, Postcode, City

Name, Contact

firstname + lastname

Fax

Fax

Phone

Telephone

JobTitle

extension_attributes.company_attributes.job_title

Download orders

Cin7 Core loads most orders from Magento automatically. You can also load orders manually. Orders loaded from Magento will remain in the Pending orders section until they are processed by Cin7 Core. Stock is allocated immediately, reducing the available quantity.

Load orders automatically

When a Magento store is connected to Cin7 Core, automatic notifications are triggered whenever a Magento order is Created, Canceled, or Deleted, or changes in status.

According to your order capture settings, Cin7 Core automatically captures an order from Magento when the order is created, paid, processing, complete, or closed. It then stores the order in the Pending orders section. Cin7 Core can take up to 10 minutes to pick up an order, because Magento may send notifications with some delay.

  • If Daily consolidation is selected, the orders will stay in Pending orders until the Consolidation time, when they will be processed as a single consolidated sale order in Cin7 Core.

  • If No consolidation is selected, the orders will be processed into sales automatically in Cin7 Core within a few minutes.

Load orders manually

Most orders load automatically from Magento. You may need to load orders manually if you want to:

  • Test the integration

  • Reload orders after loading was turned off temporarily

  • Reload orders after changing your order capture setting

  • Reload an order you previously loaded and deleted

Manually downloading more than 1 month's worth of orders at a time may lead to performance issues due to the volume of data being processed.
  1. In your Magento integration, go to the Pending orders section.

  2. Select Load orders, which will open a pop-up window.

  3. Select a date to load all orders from that date onwards.

  4. Select Load from Magento to start. This operation can take some time. You can safely close the pop-up window and leave it to run in the background. Magento allows manual downloading of orders up to 1 year old.

Load orders dialog with a date selector

View pending orders

Orders captured from Magento are stored in the Pending orders section before being converted to sales in Cin7 Core.

  1. Select the Pending orders tab of your Magento integration.

Pending orders tab in the Magento integration

Process orders

Processing a pending order converts it into a sale order in Cin7 Core. See Order field mapping for how order fields in Magento are mapped to sale order fields in Cin7 Core.

You can view all processed orders in the Log section. If an order already has an entry in the log (was imported previously), it will not be processed again. This guarantees that no duplicate sales will be created by Cin7 Core. This also means we do not capture changes made to orders after they are downloaded to Cin7 Core.

When processing orders, the logic is the same as that of the Cin7 Core UI. Dropshipping, kitting, and other important scenarios are implemented in the same way. Products that are optionally dropshipped in Cin7 Core will always be dropshipped if sold from Magento.

All line items are captured together with quantities, prices, and totals. Cin7 Core applies total order discounts and additional charges to the whole order, not line by line. This reduces the chance of discrepancies. Shipping and handling are saved as additional charges in the invoice.

Cin7 Core will apply captured payments to the associated sale invoice if payment accounts are mapped and the invoice is authorized.

Process orders automatically

Pending orders are usually processed automatically into sale orders in Cin7 Core.

  • If No consolidation is selected, the orders will be processed into sales automatically in Cin7 Core within a few minutes.

  • If Daily consolidation is selected, the orders will stay in Pending orders until the Consolidation time, when they will be processed as a single consolidated sale order in Cin7 Core.

Process orders manually

Cin7 Core automatically converts pending orders into sale orders, either within a few minutes for unconsolidated orders or once a day for consolidated orders. However, you can manually process pending orders at any time.

  1. In your Magento integration, go to the Pending orders section.

  2. Select Process. This will convert any pending orders into individual sale orders in Cin7 Core regardless of order consolidation settings.

Process button in the Pending orders section

Orders, refunds, and payments mapping

Orders and sales

Cin7 Core

Magento 2

Discounts, amounts, tax amounts

Calculated from many fields in Magento2 respecting integration logic

Customer and Customer Details (Contact, Phone, Email)

If Use Company as a Customer is disabled:

  • Customer from Magento2 sale will be used, if no customer is specified the default customer in Magento2 integration Settings will be used.

If Company name (optional) as a Customer is enabled:

  • Company name from Magento2 sale will be used with customer name as a contact. If no company name is given the customer from Magento2 will be used, if no customer is specified the default customer in Magento2 integration Settings will be used.

Billing Address, Contact

  • Billing address from Magento2 will be used. This is a mandatory field in Magento2.

  • If the billing address is not specified, the shipping address from Magento2 will be used.

  • If customer is not provided in Magento2, billing address for the default customer will be used.

Shipping Address, Contact

  • Shipping address from Magento2 will be used. Including ExtensionAttributes.ShippingAssignments

  • If the shipping address is not specified, this field will be left blank.

  • If customer is not provided, default customer shipping address will be used.

  • If Ship to different address is unchecked the billing address will be used as the shipping address.

Terms

Default payment terms (go to Settings, then Reference books, then Payment Terms).

Sales Rep

  • Sales Representative Name specified in Magento2 Settings.

  • If Sales Representative name is not specified, Magento2 store name will be used.

Account

  • Optional Revenue Account specified in Magento2 Settings

  • If Optional Revenue Account is not specified, default sales account will be used.

Tax Rules

Will be set according to Tax Rule Mapping in Magento2 settings.

Location

  • If order routing is enabled, the field will have value determined by order routing.

  • Otherwise, if Magento2 sale has fulfillment and Magento2 location is mapped to a Cin7 Core location, this Cin7 Core location will be used.

  • Otherwise default Magento2 location for online sales will be used.

Ship to Company

Company name from Magento2 if provided.

Ship to Contact

Customer contact name from Magento2 if provided.

Carrier/Service

Magento2 carrier information will be used.

If no Magento2 carrier information is provided, Local Pickup will be used.

OrderID

IncrementId

CustomerReference, CustomerNote, ShippingNotes

StatusHistories + ExtensionAttributes.GiftMessage.Message

Date

CreatedAt

Currency

OrderCurrencyCode

Order lines

Items including prices, taxes, quantities respecting type of Magento2 order: Bundle, family, Configurable and so on

Refunds and credit memo

Cin7 Core refund/credit memo

Magento 2 fields from CreditMemo

Date

CreatedAt

CustomerNote

Comments (into one string)

RefundID, RefundNumber

IncrementId

Payments

Payments using similar mapping as below

Lines (separate lines for several sources)

Combination of ShippingTaxAmount, ShippingAmount, AdjustmentNegative, AdjustmentPositive

DiscountTaxCompensationAmount, DiscountAmount

Items: TaxAmount, RowTotal, TotalPerLine, Qty, Quantity, SKU

Payments

Cin7 Core payment field

Magento 2 payment information

PaymentProcessorID

Payment.Method

Reference

IncrementId

ID

Payment.EntityId

Amount

TotalPaid

Date

CreatedAt from last of history items

Fulfill Magento orders

When you fulfill an order in Cin7 Core, Cin7 Core downloads the order according to your fulfillment processing mode. You may need to complete the pick, pack, and ship stages manually.

When a shipment is authorized in Cin7 Core and the carrier is specified, Cin7 Core will try to create order shipment information in Magento. This will only work in the No consolidation processing mode.

Only one fulfillment is pushed to Magento. If the order has multiple fulfillments in Cin7 Core, only the first fulfillment information is sent to Magento.

Cancel or delete an order in Magento

When a Magento order is canceled or deleted, Cin7 Core automatically finds and voids the corresponding sale task, if created, or removes an associated pending order if the order has not yet been processed.

View order log

Magento orders that have successfully been converted to a sale in Cin7 Core receive an entry in the Log. If an order already has an entry in the log (was imported previously), it will not be processed again. This guarantees that no duplicate sales will be created by Cin7 Core.

  1. Select the Log tab of your Magento integration.

Log tab in the Magento integration

Use X Delete to remove a log entry. Deleting a log entry will not void or delete its associated sale.

Reload an order

If for any reason you need to reload an order from Magento, Cin7 Core allows loading historical sales data a maximum of 1 year old.

  1. Void the sale. A record of this will be kept in Cin7 Core for reconciliation purposes, but the transactional data will be deleted.

  2. Return to the Magento integration Log tab and delete the log entry. This will allow the order to be recaptured from Magento.

  3. Go to Pending orders and select Load orders, making sure to set the date before the order to reload was made.

Refunds

Cin7 Core captures refunds from Magento. Cin7 Core will then capture the refund and returns/restocks and apply them to the associated sale task.

If the sale is unfulfilled, this can cause an error with restocking the unfulfilled items. These will appear on the Log as Pending fulfillment. If you are experiencing this error, you will need to enable the Ignore restock for non-fulfilled sales setting.

Submit returns request via RMA portal

Customers can submit returns requests via Cin7 Core RMA portal if your organization's subscription has this feature, allowing customers to initiate the Cin7 Core RMA workflow, and view the status of their returns. This includes sales processed through connected eCommerce channels.

Any Cin7 Core customer can submit a returns request via the RMA portal with an order number or invoice number and email address by accessing the relevant URL. We recommend adding the RMA portal URL to your default sale email template sent to customers. See detailed instructions at RMA portal for returns requests.

Refunds and restocks processed in this way are not automatically exported to the eCommerce channel, and have to be manually updated within the channel. You may prefer to use the returns workflow offered by Magento if you do not need the additional RMA workflow features in Core.

Refunds for sales predating integration with Cin7 Core

Merchants with eCommerce channels occasionally have to process returns or refunds for a sale that predates integration of the eCommerce channel with Cin7 Core.

Sales and refund information is imported automatically from the eCommerce channel to Cin7 Core, but can also be manually imported via the Cin7 Core web portal. Historical refunds and returns are handled differently for each case.

Automatic import: Cin7 Core checks the sale order date against the date of integration with the eCommerce channel. If the sale order date predates the date of integration, credit note and refund are imported without the corresponding historical sale task.

  • A sale is created without order lines or invoice lines.

  • The Credit note tab shows refunded items, and if a refund was processed in the eCommerce channel it will be captured on this tab.

  • The Restock tab is left empty and no stock adjustments are made.

Manual import: Manually loading orders from Magento functions in the same way whether the sale took place before or after integration with Cin7 Core.

  • From the Pending orders tab, select Load orders and choose a date to load sales, including historical sales as pending orders. Process the sale associated with the refund.

  • The sale order will have order, invoice, pick, pack, and ship lines. It will also have credit note and restock lines.

  • You need to perform a manual stock adjustment to correct any discrepancies from the refund.

Was this article helpful?

Have more questions? Submit a request