Magento Integration - Revision history

Russ horton: /* Magento 2.x (Work in Progress) */

2021-01-05T17:35:32Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 17:35, 5 January 2021
Line 10:		Line 10:
	Latest tested version is 1.9.3.6		Latest tested version is 1.9.3.6

	==Magento 2.x (~~Work~~ in ~~Progress~~)==		==Magento 2.x (unlikely to be supported in CMS)==
	Magento 2.x is a significant departure for 1.x both for your site and the API that CMS communicates with. There is not a good transition path to get to 1.x to 2.x for either your site or our integration so research and plan accordingly before deciding to jump to 2.x. Be sure to find out what is involved to get your new site created and coordinate with us on our timeline for support for 2.x.		Magento 2.x is a significant departure for 1.x both for your site and the API that CMS communicates with. There is not a good transition path to get to 1.x to 2.x for either your site or our integration so research and plan accordingly before deciding to jump to 2.x. Be sure to find out what is involved to get your new site created and coordinate with us on our timeline for support for 2.x.

	Magento 1.x is ~~still a supported product and currently does not have a date set for its~~ end of life (EoL). Magento is aware that there is not an easy transition from 1.x to 2.x so they are maintaining support for 1.x for some time. They have stated that they will provide at least 18 months lead time on any EoL date they announce. As such 1.x will remain a viable solution for some time.		Magento 1.x is end of life (EoL) as of June 2020.

	We are evaluating our integration options for 2.x but at this moment do not have a scheduled release date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come ~~until 2019. We'll know more in the coming months as we finish assessing the possible approaches and tools we can implement for 2.x~~.		We are evaluating our integration options for 2.x but at this moment do not have a scheduled release date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come.

	In the meantime, we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.		In the meantime, we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.

Russ horton: /* Magento 2.x (Work in Progress) */

2018-06-22T23:06:31Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 23:06, 22 June 2018
Line 17:		Line 17:
	We are evaluating our integration options for 2.x but at this moment do not have a scheduled release date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019. We'll know more in the coming months as we finish assessing the possible approaches and tools we can implement for 2.x.		We are evaluating our integration options for 2.x but at this moment do not have a scheduled release date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019. We'll know more in the coming months as we finish assessing the possible approaches and tools we can implement for 2.x.

	In the ~~mean time~~ we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.		In the meantime, we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.

	Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for ~~back order~~ and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:		Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for backorder and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:

	*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our [http://wiki.newhavensoftware.com/index.php/ECMS_Module#Generic_File_Based File Based eCMS plug-in] (sold separately). To be clear, this extension pulls new Magento orders and posts a file to an FTP site in an XML format which they can modify to meet our spec (~~some custom charges~~ from Xtento apply for this translation.)		*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our [http://wiki.newhavensoftware.com/index.php/ECMS_Module#Generic_File_Based File Based eCMS plug-in] (sold separately). To be clear, this extension pulls new Magento orders and posts a file to an FTP site in an XML format which they can modify to meet our spec (fees from Xtento apply for this translation.)
	*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing		*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing
	*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento - - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)		*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento - - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)
Line 28:		Line 28:
	It is worth noting:		It is worth noting:

	*Multiships - Magento does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets ~~charges~~ separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.		*Multiships - Magento does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charged separately for each order instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.
	*Product Data Uploads - With their extension only supports inventory level uploads, not any other product data.		*Product Data Uploads - With their extension only supports inventory level uploads, not any other product data.
	*CMS would not be communicating with a web service. These are all file based operations so would involve either manual import/exporting of files or using our eCMS module to read/write files to an FTP site. This will require some level of file management for someone to archive processed files periodically (CMS will ignore duplicate files so file archiving doesn't have to be done multiple times a day, for example.)		*CMS would not be communicating with a web service. These are all file-based operations so would involve either manual import/exporting of files or using our eCMS module to read/write files to an FTP site. This will require some level of file management for someone to archive processed files periodically (CMS will ignore duplicate files so file archiving doesn't have to be done multiple times a day, for example.)

	=Current capabilities of the base Magento Plug-in=		=Current capabilities of the base Magento Plug-in=

Russ horton: /* Magento 2.x (Work in Progress) */

2017-11-09T21:29:35Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 21:29, 9 November 2017
Line 15:		Line 15:
	Magento 1.x is still a supported product and currently does not have a date set for its end of life (EoL). Magento is aware that there is not an easy transition from 1.x to 2.x so they are maintaining support for 1.x for some time. They have stated that they will provide at least 18 months lead time on any EoL date they announce. As such 1.x will remain a viable solution for some time.		Magento 1.x is still a supported product and currently does not have a date set for its end of life (EoL). Magento is aware that there is not an easy transition from 1.x to 2.x so they are maintaining support for 1.x for some time. They have stated that they will provide at least 18 months lead time on any EoL date they announce. As such 1.x will remain a viable solution for some time.

	We are evaluating our integration options for 2.x but at this moment do not have a scheduled date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019.		We are evaluating our integration options for 2.x but at this moment do not have a scheduled release date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019. We'll know more in the coming months as we finish assessing the possible approaches and tools we can implement for 2.x.

	In the mean time we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.		In the mean time we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.

Russ horton: /* Magento 2.x (Work in Progress) */

2017-11-09T21:15:06Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 21:15, 9 November 2017
Line 26:		Line 26:
	*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)		*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)

	It is worth noting ~~that~~ Magento ~~inherently~~ does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charges separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.		It is worth noting:

			*Multiships - Magento does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charges separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.
			*Product Data Uploads - With their extension only supports inventory level uploads, not any other product data.
			*CMS would not be communicating with a web service. These are all file based operations so would involve either manual import/exporting of files or using our eCMS module to read/write files to an FTP site. This will require some level of file management for someone to archive processed files periodically (CMS will ignore duplicate files so file archiving doesn't have to be done multiple times a day, for example.)

	=Current capabilities of the base Magento Plug-in=		=Current capabilities of the base Magento Plug-in=

Russ horton: /* Magento 2.x (Work in Progress) */

2017-11-09T20:55:48Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 20:55, 9 November 2017
Line 17:		Line 17:
	We are evaluating our integration options for 2.x but at this moment do not have a scheduled date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019.		We are evaluating our integration options for 2.x but at this moment do not have a scheduled date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019.

	In the mean time we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.		In the mean time we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces inexpensive Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.

	Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:		Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:

	*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our [http://wiki.newhavensoftware.com/index.php/ECMS_Module#Generic_File_Based File Based eCMS plug-in] (sold separately).		*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our [http://wiki.newhavensoftware.com/index.php/ECMS_Module#Generic_File_Based File Based eCMS plug-in] (sold separately). To be clear, this extension pulls new Magento orders and posts a file to an FTP site in an XML format which they can modify to meet our spec (some custom charges from Xtento apply for this translation.)
	*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing		*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing
	*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento		*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento - - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)
	*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels		*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels - CMS is not currently producing output suitable for use with this module but could be done outside of CMS (by you or us.)

	It is worth noting that Magento inherently does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charges separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.		It is worth noting that Magento inherently does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charges separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.

Russ horton: /* Magento 2.x (Work in Progress) */

2017-11-09T20:52:10Z

Magento 2.x (Work in Progress)

← Older revision		Revision as of 20:52, 9 November 2017
Line 21:		Line 21:
	Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:		Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:

	*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our File Based eCMS plug-in.		*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our [http://wiki.newhavensoftware.com/index.php/ECMS_Module#Generic_File_Based File Based eCMS plug-in] (sold separately).
	*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing		*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing
	*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento		*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento

Russ horton: /* Magento 2.x */

2017-11-09T20:50:54Z

Magento 2.x

Russ horton: /* Magento 2.x */

2017-11-09T19:47:41Z

Magento 2.x

← Older revision		Revision as of 19:47, 9 November 2017
Line 21:		Line 21:
	Perhaps most interesting about Xtento's solution is that it allows CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows them to process the payments, it operates more like a standard integration where the order download into CMS '''with the credit card info''' so that CMS can handle payment processing, particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:		Perhaps most interesting about Xtento's solution is that it allows CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows them to process the payments, it operates more like a standard integration where the order download into CMS '''with the credit card info''' so that CMS can handle payment processing, particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:

	*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module]		*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our File Based eCMS plug-in.
	*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing		*[https://www.xtento.com/magento-extensions/saved-credit-cards-ccsave-for-magento2.html Magento Saved Credit Cards Module] - Enabling Magento to pass credit card data to CMS for processing
	*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento		*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento

Russ horton at 19:13, 9 November 2017

2017-11-09T19:13:37Z

@@ Line 9: / Line 9: @@
 ==Maximum==
 Latest tested version is 1.9.3.6
 =Current capabilities of the base Magento Plug-in=

Russ horton: /* Magento minimum version requirements */

2017-11-09T18:39:48Z

Magento minimum version requirements

← Older revision		Revision as of 18:39, 9 November 2017
Line 1:		Line 1:
	NewHaven Software has created an optional Magento Extension to expand the core capabilities of the Magento API and improve integration with CMS. For basic Magento deployments this extension is optional but it is required for products configured to use attributes (e.g. size and color) and Magento custom fields for data like ad code.		NewHaven Software has created an optional Magento Extension to expand the core capabilities of the Magento API and improve integration with CMS. For basic Magento deployments this extension is optional but it is required for products configured to use attributes (e.g. size and color) and Magento custom fields for data like ad code.

	=Magento ~~minimum~~ version requirements=		=Magento version requirements=
			==Minimum==
	*Enterprise 1.12.0.x		*Enterprise 1.12.0.x
	*Community 1.7.0.x		*Community 1.7.0.x
	*Go 1.1.2.x (limited support)		*Go 1.1.2.x (limited support)

			==Maximum==
			Latest tested version is 1.9.3.6

	=Current capabilities of the base Magento Plug-in=		=Current capabilities of the base Magento Plug-in=

← Older revision		Revision as of 20:50, 9 November 2017
Line 10:		Line 10:
	Latest tested version is 1.9.3.6		Latest tested version is 1.9.3.6

	==Magento 2.x==		==Magento 2.x (Work in Progress)==
	Magento 2.x is a significant departure for 1.x both for ~~the~~ site and the API that CMS communicates with. There is not a good transition path to get to 1.x to 2.x for either your site or our integration so plan accordingly before deciding to jump to 2.x. Be sure to ~~explore~~ what is involved to get your new site created and coordinate with us on our timeline for support for 2.x.		Magento 2.x is a significant departure for 1.x both for your site and the API that CMS communicates with. There is not a good transition path to get to 1.x to 2.x for either your site or our integration so research and plan accordingly before deciding to jump to 2.x. Be sure to find out what is involved to get your new site created and coordinate with us on our timeline for support for 2.x.

	Magento 1.x is still a supported product and currently does not have a date set for its end of life (EoL). Magento is aware that there is not an easy transition from 1.x to 2.x so they are maintaining support for 1.x for some time. They have stated that they will provide at least 18 months lead time on any EoL date they announce. As such 1.x will remain a viable solution for some time.		Magento 1.x is still a supported product and currently does not have a date set for its end of life (EoL). Magento is aware that there is not an easy transition from 1.x to 2.x so they are maintaining support for 1.x for some time. They have stated that they will provide at least 18 months lead time on any EoL date they announce. As such 1.x will remain a viable solution for some time.

	We are ~~exploring~~ our integration options for 2.x but at this moment do not have a scheduled date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019.		We are evaluating our integration options for 2.x but at this moment do not have a scheduled date. Be advised, due to the complexity of the integration and how much has to be done from scratch, it is possible that 2.x support may not come until 2019.

	In the mean time we have explored ~~other options~~ for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering~~. We're working with a pilot client now to try this solution out~~.		In the mean time we have explored alternatives for CMS users moving to Magento 2.x in advance of our support for it. There is a company called [https://www.xtento.com/magento-2-extensions.html Xtento] that produces Magento extensions (for both 1.x and 2.x, Community and Enterprise) that looks promising. We've reviewed our XML requirements with them and they seem quite capable of delivering.

	Perhaps most interesting about Xtento's ~~solution~~ is that ~~it allows~~ CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows ~~them~~ to process the payments, it operates more like a standard integration where the order ~~download~~ into CMS '''with the credit card info''' so that CMS can handle payment processing, particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:		Perhaps most interesting about Xtento's suite of extensions is that they allow CMS to work with Magento in a non-synchronizing mode, for better or worse. In other words, instead of synchronizing invoices and packages with Magento which allows Magento to process the payments, it instead operates more like a standard integration where the order downloads into CMS '''with the credit card info''' so that CMS can handle payment processing. This is particularly beneficial for back order and future ship (split order) processing and simplifying the integration. To accomplish this you'd need to use three of Xtento's extensions:

	*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our File Based eCMS plug-in.		*[https://www.xtento.com/magento-extensions/magento-order-export-module.html Magento Order Export Module] - Allowing orders to be imported (not downloaded) - Downloads and imports can be done manually or in conjunction with our File Based eCMS plug-in.
Line 25:		Line 25:
	*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento		*[https://www.xtento.com/magento-extensions/magento-tracking-number-import-module.html Magento Tracking Number Import Module] - Import shipped item data with tracking numbers to update status in Magento
	*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels		*[https://www.xtento.com/magento-extensions/magento-stock-inventory-import-module.html Magento Stock Import Module] (optional) - For uploading updated stock levels

			It is worth noting that Magento inherently does not support single orders with multiple recipients. This is a strength of CMS and common for B2C companies shipping gift orders. Magento instead treats each recipient as a separate order (meaning the buyer gets charges separately for each instead of one payment for all orders.) In Magento 1.x our Magento extension stitches these separate orders together so this is another important difference to be aware of between 1.x and 2.x at the moment.

	=Current capabilities of the base Magento Plug-in=		=Current capabilities of the base Magento Plug-in=