What to expect

If you are already integrated with NuORDER and switching to a new ERP, you will need a dedicated NuORDER Integration Consultant as well as a development resource for the new system integration (be sure to reach out to your Account Manager for pricing). The Project will follow the same general API or Flat File rollout & timeline as these Helpdesk articles (Integration Patterns: Things to consider for a Flat File vs API Integration / NuORDER Flat File SFTP Integration) but with some added complexities: 

NuORDER required fields  

Key identifier values on below data points will need to be considered when ERPs change, as this will result in data inconsistencies when updated. Best practices will be to have the same values in each of these fields in order to avoid duplicate records. If these required fields do need to be updated, then it is critical to have a reference table with the Key Identifiers of the old values already stored in NuORDER, and the expected new values.

Product: Season, Style Number, Color, Size or Size Groups, BrandID, UPCs.

Company: Customer Codes, Warehouse Codes, Pricesheet Names, Customer Groups.

Inventory: UPC, BrandID, or Season, Style Number, Color, Warehouse.

Pricesheets: UPC, BrandID, or Season, Style Number, Color, Pricesheet Names.

Orders: any Key identifiers your new ERP will need to successfully import an order.

Ideal timeline and resources 

In order for the project to start and finish on time with allocated resources from both you and NuORDER,  your new ERP should be fully live with real data before we start the Integration Project. Also, be mindful of resource availability if the same project team on your side is working on both the NuORDER integration and the ERP implementation. It could create conflicts in prioritization which will delay the timeline for one or both projects.