Akanksha Maheshwari

Engineering
casebook

Notes on commerce systems, data correctness, and operational failures. Each case follows a specific change and the engineering decisions behind it.

Case notes

Salesforce Merchant integrations

Which system owns the quote?

A quote starts at the point of sale. Once a merchant system receives it, it can have a newer version. I built Java flows that distinguished those two states and added React controls to configure the connector.

Source of truth and failure handling

The local record triggers the first export. On resume, the merchant supplies the latest state and the POS surfaces connector errors. I kept ordinary suspended carts local and added regression tests for both paths. The broader quote automation work supported 10+ merchant partners.

Quote ownership by operation
Create and export
Point of sale → Merchant
Resume
Merchant → Point of sale

Salesforce Retail reporting

Keeping net sales consistent across reports

I implemented net sales excluding tax across SQL, Java, and React. I aligned refund eligibility with the original sale and preserved decimal precision so hourly, sales, and reconciliation reports could use the same metric.

Data correctness

I moved the calculation into SQL across the summary and hourly query paths, preserved register join deduplication, and surfaced the metric in the React dashboards and CSV exports.

Salesforce Merchant onboarding

Keeping locale behavior consistent

During a 25-country merchant setup expansion, I aligned country, currency, and language in the React admin console with backend localization and language-specific Solr analysis.

Salesforce Search platform

Preparing retail search for Solr 9

I contributed Solr 9 index configurations for new retail locales and aligned language analysis across product, bundle, store, and image search where those indexes were used.

Language behavior and query limits

I corrected Thai tokenization and Turkish apostrophe handling for image search. In separate Solr compatibility work, I batched large product lookups to stay within Boolean clause limits and added regression tests for search and retrieval.

Salesforce Order management

Recovering order imports from MySQL deadlocks

I traced intermittent return lookup failures to deadlocks in concurrent order imports. I narrowed writes to specific primary keys and added bounded retries for transient lock failures while preserving atomic imports.

Retry boundaries

I kept post-commit processing outside the retry loop so it would run once. I verified retry and rollback behavior in regression tests, including cleanup failures that had to stop the retry.

Salesforce Admin console

Making inventory access more granular

I added permissions for adjustments, transfers, and cycle counts across the React role editor, navigation, and route guards. I preserved compatibility for roles that used a single inventory permission.

Compatibility and validation

I tested how access inherited from the parent permission, how the console handled older roles, and how users with limited access encountered guarded routes and disabled actions.

American Express Communications

Migrating a legacy template library

I built tooling to migrate more than 7,000 legacy email and letter templates. In a separate change to the same platform, caching improved message assembly performance by about 30%.

American Express Release engineering

Making communications releases repeatable

I automated Jenkins pipelines and scripted document promotion across email, SMS, and other channels. The pipeline automation cut deployment time by 50%.

AI tooling notes

Shared Retail Cloud Claude Code toolkit 24 team-maintained skills

Design and testing

prd-review
Review requirements for gaps, ambiguity, and feasibility.
create-hld
Turn requirements into a high-level design and implementation spec.
implement-hld
Guide implementation and verification from an approved design.
feature-analyze
Trace feature dependencies and assess the impact of a change.
feature-test-suite
Build test plans and API coverage across the backend, admin console, and POS app.
e2e-test-plan
Produce and run end-to-end tests from design documents.

Investigation and support

ask-retail-cloud-help
Answer product questions using documentation and code references.
check-logs
Filter application logs and trace errors to code.
fetch-from-db
Look up data to support an investigation.
gus-investigate
Triage issue tickets and document evidence and findings.
gus-investigate-v2-beta
Extend ticket investigations with shared findings and usage tracking.
investigation-log
Record findings and search prior investigations.
pos-investigate
Route POS support issues into the investigation workflow.
reproduce-scenario
Turn a POS scenario into a repeatable sequence of API requests.

Developer onboarding

setup
Prepare the development workspace and connect related repositories.
onboard
Guide developers to the setup for their area of work.
onboard-app
Set up the Swift POS app development environment.
onboard-backend
Set up the Java services and backend developer tools.
onboard-cms
Set up the React admin console and its dependencies.

Infrastructure

add-pos-stack
Guide configuration for a new POS application environment.
aws-jit-export
Help developers use temporary AWS access in their terminal.
cdk-deploy-eb
Guide review and deployment of AWS application environments.
setup-tunnels
Help developers connect to authorized application infrastructure.
tomcat
Manage a local Tomcat server and inspect its runtime state.
Personal experiment in human-reviewed AI drafting

I prototyped a Python workflow that filters public job listings by role and location, tracks application state in SQLite, and drafts responses with the OpenAI API. A person reviews every résumé claim and submits the application.

About the author

I’m Akanksha Maheshwari. I’ve worked on retail commerce at Salesforce and enterprise communications at American Express. I’m interested in what happens at system boundaries, especially when records disagree, writes contend, or older clients depend on a contract.