OSN 2.0 with Steven Stanley and the Standards Committee


Insights from the video:

Standardization and Updates

📈 Stephen Stanley will be discussing the advancements and updates in order shipment notification 2.0, providing valuable insights into the cycle of promo standards.

🔄 The purpose of OSN 2.0 was to update the standard, align it with other standards, and add missing capabilities based on feedback from end users.

🔄 The structure of OSN 2.0 is aligned with other services and the PO spec, indicating a more standardized approach to order shipping notifications.

📦 OSN 2.0 allows for more granular tracking of locations, quantities, and specific box contents, which is particularly useful for apparel suppliers.

📦 The PO standard and product data standard were crucial in making sure that the early standards created by promo standards were compatible with purchase orders, which are essential in the transactional piece.

📝 OSN 2.0, or shipment notifications, has gone through a peer review process, months of beta testing, and a vote from the membership to become a production-ready standard.

📦 Ship notification is the biggest piece of information that people need when trying to figure out what has and hasn't shipped.

Member Engagement and Feedback

🌴 Provo standards is planning a Tech Summit in February 2024 on the beach in Florida, which sounds awesome!

🗣 Members have the ability to participate in the RFS process and provide feedback to the standards committee, ensuring that their voices are heard in the decision-making process.

📝 The committee is open to considering and incorporating new information and ideas, even if they were not initially included, in order to improve the standardization process.


The key idea of the video is that Order Shipment Notification 2.0 aims to standardize and improve the clarity and implementation of standards for various aspects of order shipment, providing granular details and compatibility with product data and purchase orders.

📅 00:00 Steven Stanley discusses the advancements and implementation of order shipment notification 2.0, updating and aligning the standard with other standards and making details more granular for distributors and service providers.

📦 08:32 The Order Shipping Notification 2.0 standardizes sales orders with multiple shipments and packages, improves naming conventions, includes supplier and distributor information, and provides clarity on shipping methods and product identification.

📦 14:59 Suppliers should set up a Sandbox environment with test URLs and put all quantity and item information on the first item, while also considering that the math may not always be straightforward when determining the number of boxes based on the total quantity; OSN 2.0 aims to address issues with standardization and compatibility with product data and purchase orders, improving clarity and implementation of standards for various aspects of order shipment.

📝 21:47 The speaker emphasizes the importance of being logged in to access all content on the website, including the endpoint listing, documentation, validator, and best practices, while discussing the limitations of the current membership tool and the need for a custom solution.

📝 25:32 The speaker discusses the transition from beta to approved services, with a focus on OSN 2.0, and provides links to view and download the necessary documentation, while also mentioning the deprecation of services and the importance of upgrading to ship notification for tracking shipments.

📝 30:27 The OSN 2.0 has launched with a service and endpoint listing, allowing users to view supplier information, request credentials, and manage their endpoints and services through integration with Wild Apricot.

📝 36:15 New endpoints should be tested and verified before being posted, live and test URLs should be listed in OSN 2.0, and there is a Sandbox environment for testing web services and validating their compatibility with promoscenters.org.

📝 43:20 The Standards Committee is developing a company information service to address the issue of optional features in endpoints, and they welcome feedback to improve standardization and future road map information.