Make / quotation review
Catch a missing currency before export.
Extract the quotation fields, check the arithmetic and keep uncertain values in a review step.
In the sample One quote ready for approval. Two held for review.
Try the demo Corey / independent developer
I make your tools
work together.
I build automations for requests, supplier data and quotations, with a review step where your team needs it.
See how I approach the work.
Three independent demos with sample inputs and inspectable output. Open a case and try the part that usually goes wrong.
Product data
Keep similar models separate.
Match a supplier feed to manufacturer records. A model family stays separate from an exact configuration.
- Supplier claim
- Belkin WCH015 / 140W total
- Source check
- 200W total; 140W single port
- Decision
- Hold for review
Request handoff
Replay a request without another project.
Follow the event log through a duplicate delivery, a changed payload and a failed destination.
Try the demoWhere I can help.
A focused first stage makes the work easier to price, test and hand over.
Workflow automation
Repeated copying between forms, sheets and task tools.
CRM lead routing
Repeat enquiries creating duplicate contacts or deals.
Product data pipelines
Supplier spreadsheets that need matching, cleaning and review.
Price and stock monitoring
Price histories that mix variants, currencies or collection failures.
Document processing
Manual quotation entry with missing fields or mismatched totals.
China sourcing
Quotes that differ in pack size, MOQ or delivery terms.
My background is in product and supplier data.
I’m Corey, an independent developer based in Guangzhou. I work in English and Mandarin.
I built a product-research and sourcing workspace with 1688 discovery and detail adapters, source links, supplier comparisons and structured exports. That work shapes how I handle identifiers, inconsistent files and missing information.
The cases here are self-built demonstrations of that approach. Each includes the sample data, what I built and the result you can check.
Discuss on UpworkBegin with one useful piece of the process.
Show me a sample.
Send an anonymized input, where it should go and an example of a correct result.
Agree a paid first stage.
Define the output, review points, checks and budget cap. Broader systems can start with a discovery stage.
Review the result and handover.
Test normal and difficult cases together. Keep the working files, run notes and a clear plan for maintenance.
Who pays for APIs, hosting and outside services?
Any required API, hosting, scraping, sample or inspection costs are identified separately before approval. Your accounts and access requirements are agreed as part of the scope.
Can we use my existing tools?
That is the starting point. I review the tools and available access first, then recommend a connection or a small custom component where it is useful. The demo pages show the parts already built and tested.
Start with a small paid pilot.
Send an anonymized sample, the tool it should reach and what a correct result looks like. I will help define the scope, acceptance checks and budget before work starts.