SAP Business One order automation starts with business partner and item identities. The customer may send a purchase order using its own part numbers, while the distributor records sales against internal item codes and a specific customer account. The implementation must resolve that relationship before preparing an ERP transaction.
SAP documents business partner catalog numbers and the Service Layer, but those capabilities solve different problems. Catalog numbers help identify what was ordered; an integration interface determines how data moves. The steps below separate those decisions and define what to test in the customer's own Business One environment.
Identify the right business partner and destination
SAP's business partner documentation covers customer, vendor and lead records with associated contact, address and commercial information. An incoming customer PO belongs to the selling workflow. Match the buyer to the appropriate customer record instead of creating a new business partner from a printed company name.
Agree which entity places the order and which destination receives it. A purchasing office may order for several branches, and the address on the PDF may differ from the customer's usual delivery site. Keep the original name and address available while a reviewer selects the controlled records. Test an unfamiliar location and an account with a similar name before accepting the mapping.
Use business partner catalog numbers where they apply
SAP Business One supports customer and vendor catalog numbers alongside internal item numbers. Its setup documentation describes mappings by business partner or by item and notes that the behavior applies to Item documents rather than Service documents. This gives the implementation a concrete place to investigate existing customer-part relationships.
Ask the order team whether those mappings are complete and current. If a buyer uses code BR-20 for an internal bearing item, preserve both references when preparing the order. Do not promote a one-off guess into a permanent alias automatically. Establish who reviews a proposed mapping and how a corrected relationship is maintained in the source catalog.
Resolve the physical item before the commercial values
Industrial products often share a short description while differing in size, material or packaging. Use the customer's code, the full source description and approved catalog evidence together. An exact-looking text match can still select the wrong variant if the customer's alias is incomplete.
Then verify units and price basis. A quantity in cartons and a price per piece need an explicit item-specific conversion. Confirm any warehouse or other customer-required line information with the Business One administrator. Include a line where the product is known but the price differs; the reviewer should make a commercial decision without having to rematch the item.
Define the Service Layer contract explicitly
SAP's Service Layer documentation describes query options for entity collections, including item and order examples. Its session guidance describes login sessions and the B1SESSION cookie used on subsequent requests. Those details matter when deciding whether an existing integration component can access the customer's installation.
A connector that accepts an HTTPS URL and an API key does not automatically implement a login session, the required query format or the customer's document mapping. Have the administrator define the supported interface, network access, credentials and allowed operations. Keep read access to catalog data separate from permission to create sales documents, and test expired sessions as a recoverable condition.
Verify catalog completeness and update behavior
When a catalog is read in pages, verify that the process reaches the intended final record. A first page containing plausible items is weak evidence of a complete sync. Use a controlled test feed with items near the beginning and end, an updated description and a repeated code that should be investigated.
Define what absence means. An item missing from a filtered feed may be outside the selected range rather than deleted. Agree how disabled products, changed aliases and conflicting prices are handled before applying updates. Keep the last successful result available if the connection fails partway through, and avoid leaving reviewers with an unexplained partial catalog.
Validate the document created in Business One
For any planned direct integration, test the exact sales-document operation with representative customer POs in an approved environment. Compare the business partner, delivery destination, internal item codes, quantities, prices and required custom fields. Confirm which person or process controls the next fulfilment step.
Repeat an accepted input and simulate an uncertain response. The team should be able to identify an existing ERP record before deciding whether another attempt is safe. Keep the original file, approved order version, mapping decision and receiving record reference together so a disputed order can be traced without relying on an operator's recollection.
Scope Business One integration around the actual interface
Ordinon currently supports document review, human approval and fixed CSV exports. A compatible generic HTTPS endpoint can supply manual product catalog pulls. The current connector does not manage SAP Service Layer login sessions or automatically create Business One orders. Those capabilities require a separately implemented and validated adapter or customer import process.