THE LATEST
OCT 2026 ● Kensium POS 7.0 available from October 1ERP · ECOMMERCE · THE PEOPLE BEHIND THE SYSTEMSIN FOCUS ● Rahul Gedupudi

Founders / Connected commerce

Rahul Gedupudi wants the storefront to keep its promises

The Kensium co-founder has spent years connecting what customers see with what businesses can deliver. His career keeps returning to the same question: do the systems agree?

Advertisement

A shop window is allowed a little theatre. A stock count is expected to tell the truth. Rahul Gedupudi has spent much of his working life in the awkward space between the two, connecting the part of a business that makes promises with the part that must fulfil them. The customer sees a price and a delivery option. Somewhere behind the screen, several systems must agree that the offer is possible.

It is a practical subject for a founder to make his own. There are more photogenic corners of technology than enterprise resource planning, or ERP: the software businesses use to manage operations such as inventory and finance. Yet the consequences are wonderfully concrete. An order either travels through the business properly or creates work for somebody who had rather hoped the software would handle it.

Gedupudi, the Hyderabad-based co-founder and CEO of Kensium, has built a career around those connections. Along the way he has helped design an ecommerce connector, managed growing teams, handed over the CEO job, concentrated on products and appeared again at the head of the company. The titles move. The interest in how the machinery fits together remains recognisable.

Mumbai, Illinois, and a company of three

His technical education took him from the University of Mumbai to Illinois State University. He studied computer engineering in Mumbai, followed by a master’s in applied computer science in Illinois. The combination matters to the story because the later executive was also involved in the construction of the products. Architecture was part of his work, rather than a word borrowed for a strategy presentation.

Kensium began in 2006. Gedupudi identifies Richard Grossi and Jay Kesan as his fellow founders. An early account of the business describes a starting group of three experts, followed by growth to nearly 180 employees on its IT side by the time of a 2015 case study. These are historical figures, belonging to a particular stage of the company, when custom development was a substantial part of its identity.

The work included applications, websites and workflows, using technologies such as .NET, PHP and Java. That is a broad menu, but its items share a useful characteristic: somebody needs an existing business process to work better. Kensium’s early offering also included document management. The company was learning its customers through the jobs they needed done, across the less decorative rooms of an organisation.

2006Kensium founded
2012Acumatica work begins
2026OmnifiCX and POS modernization

The connection that became a career

In 2012, Kensium began working with Acumatica. Grossi had learned about the cloud ERP platform through a friend, and discussions followed about what the two companies could build together. The initial collaboration concerned ecommerce integration. A business selling online needed its commercial activity to connect with the system managing its operations.

Gedupudi helped architect the Magento connector with Ali Jani. Acumatica’s 2017 developer-conference biography identifies that connector as a component of its Commerce Edition and describes Gedupudi as heading product management at Kensium. Here the career becomes specific: two named collaborators, a named platform and a problem that sits between software products.

Connectors rarely receive the affection lavished on the screens they support. Their success can look uneventful: information arrives where it should, and people carry on with their work. For Gedupudi, this early collaboration established a visible line between technical design and business direction. By the 2017 conference, his remit included both Kensium’s products and where the business was going.

A review should not be a plot twist

His account of managing people is similarly interested in connections. In 2016, he described approximately 350 employees across two business units and a quarterly rhythm of formal reviews and bonuses. Annual salary increases sat alongside that more frequent feedback. These numbers describe the organisation then, rather than its size today.

His objection to treating performance management as an annual or twice-yearly appraisal was straightforward: people need feedback while they can still use it. He wanted expectations connected to daily work, company values connected to behaviour, and current performance connected to a longer career plan. He also warned against buying generic HR software and bending the process around the purchase.

“Feedback should be a continuous activity”Rahul Gedupudi, 2016

There is a modest courtesy in that approach. An employee should not need the suspense of a detective novel to discover how the year has gone. Gedupudi’s emphasis was on education for employees and managers, with individuals taking initiative to seek feedback. The tool, the review and the rating were useful only insofar as they helped people understand what to do next.

Stepping out of the chair

In 2021, after more than 15 years with Kensium, he announced that he was stepping down as CEO. Paul Prickett would take over. Gedupudi would remain on the board and lead product development, returning to a role with more technical work. He said the company had been preparing the succession for over a year.

The announcement also made room for life outside that particular job: more time with family, continuing leadership commitments elsewhere and an interest in backing new ventures. It was a change in the allocation of his time, with a continuing place inside the business he had helped found. Product development offered another way to contribute to its direction.

By May 2023, Kensium was describing him as co-founder and chief product officer. That month, he publicly congratulated human-resources leader Sharmilaa Kannan on a people-management award, recognising her communication, teamwork and contribution to the company’s culture. It is a small episode, but it places the product executive inside a company of colleagues with careers of their own.

By July 2024, Kensium was again identifying Gedupudi as CEO. His career had acquired a succession chapter and a product chapter without ending its leadership story. The sequence is more interesting than an uninterrupted string of executive titles: a founder can remain involved while the work, and the formal responsibility, change shape.

Buying focus, adding design

That July brought a transaction with two directions. Net at Work acquired Kensium’s Acumatica practice, including its consultants, operations and most of that practice’s customer base. Kensium acquired Pixafy, Net at Work’s ecommerce agency. The acquisitions were completed on July 26, 2024, with a strategic alliance connecting the businesses afterwards.

The Acumatica-practice transfer gave Net at Work an office and a 40-member team in Hyderabad. For Kensium, Pixafy added ecommerce capabilities and supported a broader range of ERP choices. Gedupudi welcomed the Pixafy team while expressing confidence in Net at Work as a home for the Acumatica customers and staff moving across. The decision involved people and customer relationships as well as software.

In January 2025, Kensium announced another acquisition: 99xStudio, the UX and UI design studio founded by Anusha Chiyadu. Gedupudi described a combination of design and technology. The addition brought the customer’s experience further into a business already concerned with what happens behind it. A workable operation still needs an interface a person can understand without negotiating a private treaty with the screen.

The register gets its turn

The product work became especially visible in 2026. In a January discussion with John Masi, Kensium’s vice president of client experience, Gedupudi addressed the modernization of Kensium POS. The conversation acknowledged difficulties in the existing system, including a complicated architecture, fragmented administration and slow synchronization for large datasets.

The proposed direction included a unified codebase, central administration, a browser-based interface and stronger offline operation. Discussing those changes meant dealing with the inheritance of an established product: existing customers, existing workflows and the consequences of an upgrade. Modernization carries a less glamorous obligation than a fresh launch. People already depend on what is being changed.

In September, Gedupudi’s introduction to Kensium POS 7.0 announced availability from October 1 for Acumatica, Sage 100 and Sage 500. The proposition put the ERP in charge of inventory, pricing, customer and financial information, with the register working from that foundation. Offline sales, payments and tax calculation were among the published capabilities, with transactions synchronizing when connectivity returned.

Those details bring an abstract architecture argument down to the counter. A retailer’s software must account for the moments when conditions are inconvenient. The connection can disappear while the customer remains, entirely reasonably, interested in completing a purchase.

THE OPERATING IDEA · ERP-LED COMMERCE
ERPInventory · Pricing · Customers
Online storeSales counterMarketplace

A conceptual illustration of Gedupudi’s stated approach: customer-facing channels work from governed operational information.

His OmnifiCX presentations in the same year widened that view beyond the register. In a February webinar, later recapped in March, he explained a shared commerce data model spanning ERP, ecommerce, point of sale, warehouse and marketplace environments. Orders, products, customers and inventory would pass through a common operational layer. The intended benefit was consistency across systems with different jobs.

A June conversation with Tim Rodman on the ERPSeal podcast covered online selling, multiple channels, AI and OmnifiCX. The setting suited the subject: a discussion about the practical difficulty of making a modern commerce operation function across its parts. As more tools become available, the old question of whether the underlying information can be trusted acquires new consequences.

ERPSeal episode 176 promotional artwork featuring Rahul Gedupudi and the topic Buying and Selling Online
Many channels, one conversation. Gedupudi’s ERPSeal appearance takes the systems argument on air. Episode artwork: ERPSeal. Watch the discussion ↗

A fondness for the long drive

Away from software, Gedupudi enjoys rallying and long drives. His biography also records an enthusiasm for endurance driving and Michael Schumacher. The interest provides a welcome glimpse beyond the executive job description. A person can care about quarterly feedback and still appreciate a fast car.

At Kensium, his current leadership remit includes AI-enabled development and testing, changes to agile delivery and an emphasis on customer outcomes. The practical standard he offers is concise: “The best solutions start by meeting customers where they are and fixing what truly matters.” It is a useful sentence to set beside the connectors, the acquisitions and the product roadmap.

Across those chapters, Gedupudi keeps returning to work whose effects are felt by somebody else: an employee understanding a review, a customer receiving a dependable price, a shop completing a sale. The storefront may have its theatre. Behind the curtain, someone still has to make the accounts agree.

Keep the conversation going