How Aeskins Pharmaceuticals integrated Magento, TOTVS, WMS and AWS to control orders and fulfillment
See how Aeskins Pharmaceuticals structured Magento, TOTVS, WMS and AWS with RDS, Load Balancing, Route 53, CloudFront and firewall rules.
After adapting Magento for the commercial operation, Aeskins Pharmaceuticals' next challenge was connecting order entry to the ERP. An order placed by an external sales rep could not end inside the e-commerce platform. It needed to move through a clear operational path with validation, credit check, approval, billing preparation, fulfillment, and tracking.
The integration was designed between Magento, TOTVS, WMS and AWS. Magento worked as the commercial entry point, while TOTVS remained the central system for business rules, credit analysis, approval, and billing. WMS handled the operational fulfillment layer, including picking, shipping, and tracking. AWS supported the infrastructure needed to keep the operation available, secure, and prepared for data exchange between systems, using RDS, Load Balancing, Route 53, CloudFront, and firewall rules.
Order approval flow in TOTVS
In TOTVS, I designed an approval flow so orders could pass through the correct stages before billing. This included credit consultation and release, analysis of commercial conditions, and validation of the payment type. In a pharmaceutical B2B operation, this control is essential: not every order should move directly to billing without checks.
The flow needed to support different payment methods, such as invoiced payment, upfront payment, and credit card. Each modality has different implications for credit, collection, risk, and release. For that reason, the integration was not only technical; it translated commercial rules into a traceable operation between the digital channel and the ERP.
WMS for fulfillment and tracking
The WMS integration connected approved orders to the logistics operation. After commercial and financial validation, the order needed to move into picking, shipping, and tracking without relying on parallel controls. This step closed the cycle between sales, billing, and delivery, creating more visibility into the operational status of each order.
With WMS integrated, Aeskins could better monitor fulfillment and reduce noise between commercial, finance, and logistics teams. The order stopped being only an ERP record and gained operational continuity through delivery, with tracking information organized for internal follow-up and customer support.
AWS with RDS, Load Balancing, Route 53 and CloudFront
The AWS layer was important to bring stability and control to the architecture. The application ran on a foundation prepared for availability, while RDS separated the database from the application layer. Load Balancing helped distribute traffic and reduce bottlenecks; Route 53 organized DNS and routing; and CloudFront accelerated content and Magento asset delivery.
Security was also treated as a central part of the architecture. I applied AWS firewall rules to limit access and protect critical components of the operation. In a flow connecting e-commerce, ERP, WMS, and billing, controlling who can access the application, database, and integrations is as important as maintaining performance.
Integrations between e-commerce and ERP need to handle availability, failures, logs, security, and data consistency. The infrastructure was designed to support this exchange without leaving the operation dependent on manual processes or scattered files.
The design also helped reduce operational errors. When an order enters through a standardized flow, with customer, items, terms, and payment structured, the team gains more predictability. Approval stops being an informal sequence of validations and becomes an operational pipeline connected to billing.
From external order to billing
The main gain was connecting the commercial front and the back office. The external sales rep could register the order in the digital environment, and the company could proceed with approval, credit, and billing inside a controlled logic. This brought Magento closer to Aeskins' actual operation and reduced the distance between sales, ERP, and finance.
The result was a more mature architecture for B2B sales: Magento as the order channel, TOTVS as the approval and billing core, WMS as the fulfillment and tracking layer, and AWS with RDS, Load Balancing, Route 53, CloudFront, and firewall rules as the technical foundation for integration, availability, and security.
Continue Reading
How Aeskins Pharmaceuticals adapted Magento for e-commerce and external sales reps
Read the Aeskins Pharmaceuticals case: Magento development, commercial journey design, and store customization for external sales reps to place orders.
How Aeskins Pharmaceuticals structured full-funnel growth with data and positioning
Read the Aeskins Pharmaceuticals case: full-funnel strategy, data lake with BigQuery and Power BI, positioning, inbound and outbound marketing.
Why system integration via API means the end of manual tasks
System integration via API eliminates rework and connects ERP, CRM, and E-commerce. See how to automate your commercial operation and scale fast.