Shopify relies on Postman for more than just development
Company Size
1,000+
Region
- America
Country
- Canada
- United States
Product
- Shopify API
- Polaris design system
- Liquid templating language
Tech Stack
- Ruby
- React
- GraphQL
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Customer Satisfaction
- Productivity Improvements
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
- Platform as a Service (PaaS) - Application Development Platforms
Applicable Industries
- E-Commerce
- Retail
Applicable Functions
- Business Operation
- Sales & Marketing
Services
- Software Design & Engineering Services
About The Customer
Shopify is a leading commerce platform that provides a range of services including product listings, inventory management, payments, secure checkout, and shipping. Since its inception in 2006, Shopify has grown to over 500 engineers across offices in Ottawa, Toronto, Montreal, Waterloo, and San Francisco. The platform supports more than 500,000 merchants and processes more than $40 billion in sales through its platform. The core application of Shopify is one of the largest built using Ruby on Rails. The company also developed its own Polaris design system and the popular Liquid templating language to support their community.
The Challenge
Shopify, a leading commerce platform, provides hundreds of endpoints for all the touchpoints of commerce. The platform helps more than 500,000 merchants and processes more than $40 billion in sales through its platform. The core application is one of the largest built using Ruby on Rails. However, with thousands of partners using the Shopify API to build apps on the platform, bugs are bound to occur. The escalated support teams at Shopify needed a reliable tool to help reproduce the request and debug the issue. Additionally, the Developer Experience team at Shopify needed to simplify the process of working with APIs for developers and make the experience as smooth and enjoyable as possible.
The Solution
Shopify turned to Postman, a popular API client, to help with their development, debugging, and documentation needs. Postman is used by the escalated support teams at Shopify to reproduce requests and debug issues. It allows them to isolate every element of the request, making it easier to troubleshoot issues. The Developer Experience team at Shopify uses Postman to simplify the process of working with APIs. They published the 'Run in Postman' button to share Postman collections in their developer documentation. Once a developer enters their Shopify credentials, they can use Postman to directly access and interact with their shop data. In addition to publishing shared collections, the Developer Experience team published a tutorial for partners showing how Postman can send and capture requests to Shopify API endpoints.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Improving Production Line Efficiency with Ethernet Micro RTU Controller
Moxa was asked to provide a connectivity solution for one of the world's leading cosmetics companies. This multinational corporation, with retail presence in 130 countries, 23 global braches, and over 66,000 employees, sought to improve the efficiency of their production process by migrating from manual monitoring to an automatic productivity monitoring system. The production line was being monitored by ABB Real-TPI, a factory information system that offers data collection and analysis to improve plant efficiency. Due to software limitations, the customer needed an OPC server and a corresponding I/O solution to collect data from additional sensor devices for the Real-TPI system. The goal is to enable the factory information system to more thoroughly collect data from every corner of the production line. This will improve its ability to measure Overall Equipment Effectiveness (OEE) and translate into increased production efficiencies. System Requirements • Instant status updates while still consuming minimal bandwidth to relieve strain on limited factory networks • Interoperable with ABB Real-TPI • Small form factor appropriate for deployment where space is scarce • Remote software management and configuration to simplify operations
Case Study
How Sirqul’s IoT Platform is Crafting Carrefour’s New In-Store Experiences
Carrefour Taiwan’s goal is to be completely digital by end of 2018. Out-dated manual methods for analysis and assumptions limited Carrefour’s ability to change the customer experience and were void of real-time decision-making capabilities. Rather than relying solely on sales data, assumptions, and disparate systems, Carrefour Taiwan’s CEO led an initiative to find a connected IoT solution that could give the team the ability to make real-time changes and more informed decisions. Prior to implementing, Carrefour struggled to address their conversion rates and did not have the proper insights into the customer decision-making process nor how to make an immediate impact without losing customer confidence.
Case Study
Digital Retail Security Solutions
Sennco wanted to help its retail customers increase sales and profits by developing an innovative alarm system as opposed to conventional connected alarms that are permanently tethered to display products. These traditional security systems were cumbersome and intrusive to the customer shopping experience. Additionally, they provided no useful data or analytics.
Case Study
Ensures Cold Milk in Your Supermarket
As of 2014, AK-Centralen has over 1,500 Danish supermarkets equipped, and utilizes 16 operators, and is open 24 hours a day, 365 days a year. AK-Centralen needed the ability to monitor the cooling alarms from around the country, 24 hours a day, 365 days a year. Each and every time the door to a milk cooler or a freezer does not close properly, an alarm goes off on a computer screen in a control building in southwestern Odense. This type of alarm will go off approximately 140,000 times per year, equating to roughly 400 alarms in a 24-hour period. Should an alarm go off, then there is only a limited amount of time to act before dairy products or frozen pizza must be disposed of, and this type of waste can quickly start to cost a supermarket a great deal of money.
Case Study
Supermarket Energy Savings
The client had previously deployed a one-meter-per-store monitoring program. Given the manner in which energy consumption changes with external temperature, hour of the day, day of week and month of year, a single meter solution lacked the ability to detect the difference between a true problem and a changing store environment. Most importantly, a single meter solution could never identify root cause of energy consumption changes. This approach never reduced the number of truck-rolls or man-hours required to find and resolve issues.
