2025–2026 · B2B application

Engro Humsafar

Angular product for Engro Fertilizers: dealer orders, payments, and shipments, plus admin setup for users, roles, and SAP reports.

Role
Full-Stack Developer
Timeline
Feb 2025 – present
Domain
Fertilizer dealer operations
Status
Ongoing
Client
Engro Fertilizers, via MT Pixels
Engro Humsafar dealer dashboard with sales, credit, and account balance
Dealer dashboard for orders, credit, sales, and account balance.

02 / Overview

Overview

Engro Humsafar is a private Angular product for Engro Fertilizers, still in progress. Dealers and field employees place orders, follow payment and warehouse pickup, and track shipments. Admins manage users, dealers, roles, product and warehouse setup, and reports linked to SAP, Engro's enterprise system. A Payer (the dealer), Regional Sales Manager, Trucker, Logistic, or Warehouse Incharge moves an order. The screens shown are that order flow.

03 / Context

Context

Built at MT Pixels for Engro Fertilizers. Still in progress. Field roles are Payer (the dealer), Regional Sales Manager, Trucker, Logistic, and Warehouse Incharge. Admins handle users, setup, and SAP-linked reports. There is no public URL.

04 / Problem

Problem

Five field roles have to move the same order, and five payment types change what happens after approval, without five copies of the order flow. Admins still have to set up the users, products, warehouses, and SAP reports that operation depends on.

Constraints

  • Private. Dealers and field employees place and move orders. Admins handle users, setup, and reports.
  • Five field roles: Payer, Regional Sales Manager, Trucker, Logistic, and Warehouse Incharge.
  • A dealer signs in, accepts a disclaimer, and in some cases selects a payer before ordering.
  • Five order types: Cash, Bank Guarantee (a bank promises to pay), DCF, TCI, and Unsecured (credit without that guarantee).
  • Ongoing since February 2025.

05 / My role

My role

I built Engro Humsafar: the order flow, payment, authority letters, shipments, and dealer reports, and the admin setup for users, roles, warehouses, and SAP reports.

What I built

  • Orders, payment, authority letters (documents that authorize warehouse collection), shipments, profile, and payer selection
  • Disclaimer and payer selection before an order can be placed
  • Dealer reports for payment, pending orders, certificates, bank guarantees, and SAP tracking
  • Admin sign-in, users, dealers, roles, and permissions
  • Products, banks, warehouses, pricing, the sales hierarchy, advertisements, and notification settings
  • Reports for orders, payments, dealers, and SAP

How it is structured

  • One order flow that follows the payment type through approval, pickup, and shipment

06 / Approach

Approach

Payment type is stored on the order. Cash, Bank Guarantee, DCF, TCI, and Unsecured change pickup, credit, and which role acts next. Admin setup covers the users, warehouses, pricing, and SAP reports around that same operation.

07 / Key decisions

Key decisions

01 / Decision

Field roles share one order flow. Admins work on users, setup, and SAP reports.

Reason
A dealer placing an order and an admin maintaining warehouses or a SAP report are different jobs on the same operation.
Trade-off
The order path has gates for the dealer, and setup screens the dealer does not use.
Result
Payer, Regional Sales Manager, Trucker, Logistic, and Warehouse Incharge move the order. Admins manage users, setup, and the reports.

02 / Decision

One order flow serves five payment types. The type travels with the order.

Reason
Cash, Bank Guarantee, DCF, TCI, and Unsecured each change pickup, credit, and what that role can do after approval.
Trade-off
The dealer passes gates before the first product line: a disclaimer, and a payer when one is required. After approval, the type still changes the path.
Result
Warehouse pickup and shipment follow the payment type on that order, instead of a separate flow per type.

08 / Solution

Solution

A dealer reaches a new order only after the disclaimer and, when required, a payer. The summary step shows payment, transport, and products for that type. The order screenshot is a cash order. Admins manage users, dealers, roles, products, banks, warehouses, pricing, the sales hierarchy, advertisements, notifications, and SAP-linked reports.

Engro Humsafar cash order summary after the order steps
Cash order summary after payment, transport, and product steps.

09 / Stack

Methods and technology

Methods

  • 01Payment type stored on the order and read after approval
  • 02Disclaimer and payer selection before the first product line
  • 03Admin setup for users, warehouses, and SAP-linked reports

Technology

  • 01Angular
  • 02TypeScript
  • 03RxJS
  • 04PrimeNG
  • 05PrimeFlex
  • 06Chart.js
  • 07REST API client

10 / Scope

Scope

Field roles
Five roles on the order: Payer, Regional Sales Manager, Trucker, Logistic, and Warehouse Incharge.
Order types
Five order types on one flow: Cash, Bank Guarantee, DCF, TCI, and Unsecured.
Admin setup
Users, dealers, roles, products, warehouses, pricing, the sales hierarchy, and SAP-linked reports.