The Chemistry’s Right for Betachem: Streamlined Distribution for Importer
Company Size
11-200
Region
- America
Country
- United States
Product
- Sage 100 Standard ERP
- Sage SalesLogix Sales
- Return Merchandise Authorization module
Tech Stack
- ERP System
- CRM Software
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Customer Satisfaction
- Productivity Improvements
Technology Category
- Functional Applications - Enterprise Resource Planning Systems (ERP)
Applicable Industries
- Pharmaceuticals
Applicable Functions
- Business Operation
- Sales & Marketing
Use Cases
- Inventory Management
- Supply Chain Visibility
Services
- System Integration
About The Customer
Betachem is a pharmaceutical ingredients importer based in Upper Saddle River, New Jersey. The company was founded a generation ago when the founder recognized a business opportunity in generic drugs. Betachem imports pharmaceutical ingredients from Europe and India and resells them to U.S. generic pharmaceutical companies. These firms add coatings and other additives to make end products approved by the FDA and eventually sold in the marketplace. The company operates from one location and has a staff of 12 employees.
The Challenge
Betachem, a pharmaceutical ingredients importer, was using an outdated proprietary system for its accounting functions until 1998. The company was in need of a comprehensive package that could automate both the accounting and operational sides of its business. This included maintaining batch and lot data, monitoring returned products, and providing a better-informed sales force. Additionally, the company faced challenges with returned merchandise, a common issue in the pharmaceutical industry. Minor shipping damages could render an entire drum of product unusable, and many of Betachem’s customers, large, publicly traded companies, required Return Merchandise Authorization (RMA) numbers on all returned goods. Previously, numbers were assigned by hand using a log, and fulfillment instructions were maintained elsewhere. The entire return process took five separate steps.
The Solution
Betachem implemented Sage 100 Standard ERP, a comprehensive package that automated both the accounting and operational sides of the business. The system was able to track many types of data, including custom fields like drug master file numbers and source manufacturers, which were required to appear on invoices. The system also streamlined operations, increasing efficiencies by one-third. Additionally, Betachem powered up its sales force with Sage SalesLogix Sales, a customer relationship management (CRM) software that is integrated with Sage 100 ERP. To address the issue of returned merchandise, the company implemented the Return Merchandise Authorization (RMA) module for Sage 100 ERP. This module centralized and automated all return functions, generating all appropriate transactions including credit memos, replacement orders, and purchase orders. An inquiry program determined the status of a return, and a Return Reason Report helped identify recurring issues with vendors or shippers.
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
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
Drug Maker Takes the Right Prescription
China Pharm decided to build a cloud-based platform to support the requirements of IT planning for the next five to ten years which includes a dynamic and scalable mail resource pool platform. The platform needed to have the following functions: all nodes support redundancy, ensuring service continuity and good user experience, simple and easy-to-use user interfaces for end users and administrators and good compatibility and supports smooth capacity expansion.
Case Study
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.
