Javier Gonzalez Noha

Selected work / E-commerce systems

Historical commerce engineering

E-commerce Systems

Four separate applications I developed at UA International for multichannel synchronization, mobile product publishing, competitive eBay pricing, and inventory and order operations.

Company
UA International
Role
Web Developer & E-commerce Integration Engineer
Period
February 2016–December 2021
Scope
Four separate applications
Evidence
Historical professional accomplishment

01 / Application overview

Four operational problems. Four distinct systems.

These applications share employment context, not a fictional common runtime. Each card preserves its own purpose, stack, and documented scale.

01

Multichannel integration

Multichannel commerce integration

Connected Flxpoint and vendor data with product synchronization across eBay, Amazon, Facebook, and Shopify.

Verified stack
AWS · DynamoDB · GraphQL · React · Redux · Semantic UI
Documented scope
Approximately 35,000 products
02

Mobile publishing

Mobile product publishing

An Android application that enabled marketing users to publish new products to multiple channels at once.

Verified stack
React Native · Redux · Material UI
Documented scope
No product-count figure retained
03

Marketplace intelligence

Competitive eBay pricing

Analyzed competitive eBay pricing and applied configurable rules to support marketplace pricing decisions.

Verified stack
eBay marketplace integration; framework and datastore unconfirmed
Documented scope
No product-count figure retained
04

Operations management

Inventory and order management

Centralized inventory, customer orders, shipping labels, and tracking in an operational interface.

Verified stack
Node.js · Express.js · MongoDB · React · Redux · Semantic UI
Documented scope
Approximately 25,000 products

02 / Engineering architecture

Separate boundaries, shown without false dependencies.

The retained evidence supports four application-level views, not one shared platform diagram. Each path below is intentionally independent.

Labels name only confirmed channels, responsibilities, and technologies. Missing historical implementation details remain undisclosed rather than inferred.

Four independent historical application architectures: vendor and Flxpoint data synchronized through a commerce integration application to marketplaces and Shopify; an Android publishing application published product data to multiple channels; an eBay pricing application used marketplace pricing data and configurable rules; and an operations application connected a React interface to a Node and Express API backed by MongoDB for inventory, orders, labels, and tracking.

Independent application boundaries

01

Multichannel integration

Vendor + Flxpoint data→AWS / GraphQL / DynamoDB application→eBay · Amazon · Facebook · Shopify
02

Mobile publishing

Marketing user→React Native Android application→Multiple sales channels
03

eBay pricing

Competitive eBay prices→Pricing rules application→Pricing decisions

Framework and datastore are not confirmed.

04

Inventory + orders

React operations UI→Node.js / Express.js + MongoDB→Inventory · Orders · Labels · Tracking

03 / Engineering highlights

Software shaped around commerce operations.

The work spans integration, mobile tooling, marketplace analysis, and back-office operations across five years.

01Documented scale

Multichannel synchronization across approximately 35,000 products

The integration application connected vendor and Flxpoint data with eBay, Amazon, Facebook, and Shopify while retaining a distinct AWS, DynamoDB, GraphQL, React, and Redux stack.

02

Mobile publishing workflow

A React Native Android tool gave marketing users a purpose-built path for publishing new products across multiple channels.

03

Configurable pricing analysis

A separate application combined competitive eBay pricing inputs with configurable rules to support marketplace decisions.

04

Centralized operations

A Node.js, Express.js, MongoDB, and React application brought inventory, orders, shipping labels, and tracking into one operational interface.

05

Clear application ownership

I personally developed each application; no claim is made about sole authorship, team management, or formal architecture authority.

04 / Technical challenges

Historical decisions, stated at the evidence boundary.

  • Channel-specific behaviorThe multichannel and publishing applications had to present common operational workflows across distinct sales channels.
  • Product synchronizationThe documented integration connected vendor and Flxpoint data with four external commerce destinations at meaningful catalog scale.
  • Operational usabilityMobile publishing and centralized order tooling moved repeat commerce work into interfaces built for marketing and operations users.
  • Pricing configurabilityThe eBay application separated competitive inputs from configurable pricing rules; deeper implementation details are not retained.
  • Accuracy over reconstructionNo unified platform, shared runtime, undocumented framework, performance result, or business outcome is inferred from incomplete historical records.

Historical professional work

These are four separate applications developed during my UA International employment from 2016 through 2021. Employer source code and internal design records are not available in this portfolio, so the case study stays at the verified application, responsibility, stack, channel, and scale boundaries. It does not claim performance, revenue, labor savings, uptime, conversion, team size, or management responsibility.