Partner Portal
Scharf Consulting — Ecommerce operations & systems consultant. Everything we track about our partnership in one place: referrals and where each one stands, what the referral fee comes to and when, and the reports and reference material we have built for you.
Written out so there is never any guessing. If anything here does not match your understanding, say so and we will fix it here first.
“My referral agreement, you pay 60 days after you are paid (or sooner if you want). I didn't want to put in onerous requirements. Once they start paying, set a recurring payment for 10%.” — Scott Scharf, Slack #scottscharf, 2026-01-05
“If you give me an amount, the total, I will setup an invoice in my Xero and it will have a payment link to send an ACH. A recurring invoices.” — Scott Scharf, Slack DM, 2026-02-26
“Patti just rebuilt our automation to track referral fees and we sent the first invoice today.” — Scott Scharf, Slack #scottscharf, 2026-03-04
One row per referral that has started paying. Each square is a month inside that referral's 12-month window — hover for the amount.
Live production tenant since 2026-03-04. Recurring $1,500/mo Level 2 subscription, current and active in Stripe. The $5,950 of custom development (Veracore field mapping, relative pricing tiers, Faire integration) is project work and sits outside the commission basis.
Signed and paid the deposit; go-live is this week. Applying the same rule we used for A Bar Above — the deposit month is month 1 — the window opened in June 2026, so June and July are already accrued and invoiceable now. The $5,000 Odoo 3PL integration is custom development; the $200/mo TrackStar–Mintsoft line is a pass-through we bill at cost.
Both active referrals combined, so the invoice total for any given month is a single number.
| Month | Made up of | Fee | Cumulative | Status |
|---|---|---|---|---|
| Jan 2026 | A Bar Above $150 | $150 | $150 | accrued |
| Feb 2026 | A Bar Above $150 | $150 | $300 | accrued |
| Mar 2026 | A Bar Above $150 | $150 | $450 | accrued |
| Apr 2026 | A Bar Above $150 | $150 | $600 | accrued |
| May 2026 | A Bar Above $150 | $150 | $750 | accrued |
| Jun 2026 | A Bar Above $150, Rouge $150 | $300 | $1,050 | accrued |
| Jul 2026 | A Bar Above $150, Rouge $150 | $300 | $1,350 | accrued |
| Aug 2026 | A Bar Above $150, Rouge $150 | $300 | $1,650 | scheduled |
| Sep 2026 | A Bar Above $150, Rouge $150 | $300 | $1,950 | scheduled |
| Oct 2026 | A Bar Above $150, Rouge $150 | $300 | $2,250 | scheduled |
| Nov 2026 | A Bar Above $150, Rouge $150 | $300 | $2,550 | scheduled |
| Dec 2026 | A Bar Above $150, Rouge $150 | $300 | $2,850 | scheduled |
| Jan 2027 | Rouge $150 | $150 | $3,000 | scheduled |
| Feb 2027 | Rouge $150 | $150 | $3,150 | scheduled |
| Mar 2027 | Rouge $150 | $150 | $3,300 | scheduled |
| Apr 2027 | Rouge $150 | $150 | $3,450 | scheduled |
| May 2027 | Rouge $150 | $150 | $3,600 | scheduled |
| Total, both windows | $3,600 |
Complete and honest, including the ones we dropped. Each card shows where the referral came from in your own words, so the record is auditable from both sides.
Live production tenant. Won 2026-03-04. Currently on Level 2 at $1,500/mo plus $5,950 of delivered custom development.
How it came in Scott posted the ECF forum thread — “Ugh, awful fractional SC / ERP delay, what do I do?” — and asked whether SKU.io could handle A Bar Above.
“Review this thread and let's talk how Sku.io can handle A Bar Above. Julia has been jerked around and I want to see if there is a fit.”— Scott, 2025-11-05
Signed, deposit paid 2026-06-05, Odoo 3PL integration built and paid in full. Go-live this week.
How it came in Scott included SKU.io in the IMS recommendation for Rouge.care and briefed us on the founder's situation before the demo.
“Hey, I am going to include Sku.io on the recommendation for Rouge.care, the Canadian company, tomorrow!! Can we have a quick conversation to review their requirements?”— Scott, 2026-04-07
Call held 2026-06-22, went well. Pricing discussion opened 2026-06-25. Demand planning is the centre of the deal.
How it came in Scott's intro; they were writing up their ideal demand-planning requirements.
“They need the basics (and want everything). They are working on a write up of their perfect demand planning solution.”— Scott, 2026-06-18
Demo delivered 2026-07-28. Largest open referral in the book. Pricing ($4,000/mo) was set by Scott in his selection work, not by us.
How it came in Scott's active IMS-selection engagement. $20M seller, 16 SKUs, 85% Amazon FBA/AWD plus Walmart WFS, TikTok and WooCommerce.
“I am working on the IMS Selection for an active client, wholesome foods, 16 skus, 85% Amazon fba/awd, Walmart wfs, TikTok, wfs, woocommerce. $20M. I think SKU is perfect.”— Scott, 2026-06-24
Discovery call held 2026-07-09. Cin7 switcher. Expected close 2026-08-31.
How it came in ECF. Scott spoke to them first and handed over the contact.
“New referral, ECF, Just talked to them. Gloria Hwang. Want to move off of Cin7.”— Scott, 2026-07-07
Never converted into a pipeline record on our side. Cin7 switcher. On us to re-open.
How it came in ECF, friend of Wes. Scott recommended Prediko at the simple end and SKU.io above it.
“I just recommended that Ben Porter look at sku.io (in ECF and friends with Wes). He is looking to get rid of Cin7.”— Scott, 2025-11-11
Never converted into a pipeline record on our side. Shopify + Amazon FBA + B2B on Zoey. This one is on us, not you.
How it came in ECF. Scott recommended SKU.io highly and passed the contact directly.
“New referral - Seth Spears, just recommended you highly. ECFer. Basics Shopify, Amazon FBA, B2B (using Zoey.com that I love, they would need an integration).”— Scott, 2026-02-10
Never converted into a pipeline record on our side. ChannelAdvisor incumbent. On us to re-open.
How it came in ECF. Scott asked us to add him to the referral list at the start of his own conversation.
“Add Richard Arkell to my referral list, just started talking with him, mentioned you. ECF, using Channel Advisor.”— Scott, 2026-02-19
Closed 2026-01-26 — went with another vendor.
How it came in Scott built SKU.io into his IMS recommendation for Kilne and made the email intro on 2025-12-02.
“I will be pinging you as I build sku.io into my IMS recommendation for Kilne.”— Scott, 2025-11-21
Closed 2025-12-30 — went with another vendor. Scope included consignment, product expiry, 3PL and OCR document matching.
How it came in Part of Scott's late-2025 batch of IMS recommendations; he supplied the order-volume history himself.
“For The Jilly Box. Please confirm the custom dev for the following enhancements: Consignment, Product Expiration, 3PL Integration, AI/OCR document processing for Purchase Orders.”— Scott, 2025-12-02
Closed 2026-01-26 — Cin7 was the better fit, as you called at the time of the intro.
How it came in ECF. Scott flagged the fit risk in the same message as the intro.
“New referral. Colleen Mook. ECF, been trying to decide on an IMS for a year. Nice. Cin7 is a better fit with a live, quote/order/invoice/payment workflow.”— Scott, 2025-12-02
Closed 2026-03-11 — decided to build in-house.
How it came in A former client of Scott's; he asked us to look for the intro and vouched for the team.
“You can drop ZipString. They think they can vibe code their IMS needs (having never used one and think their business is “simple”).”— Scott, 2026-03-11
Closed 2026-07-27 — never engaged after the intro. Logged retroactively in a referral audit so the record is complete.
How it came in Email intro “Introductions - Wunderfood & Sku.io” on 2026-05-21.
“BTW wunderfood never replied.”— Scott, 2026-07-07
If these close at the prices currently quoted, this is the fee each one generates across its full 12-month window. Nothing here is committed — it is what is on the table.
The Caviar Co is a SKU.io tenant we introduced to Scharf Consulting. Their fractional CFO firm, Amplēo, was brought in during a difficult period on our side, and we recommended Scott for the operations and change-management work. Kevin Hix booked with Scott the same day as the intro. Nothing about that engagement generates a referral fee to Scott — it is us sending consulting work his way under the same mutual agreement, in the opposite direction.
Introduced Kevin Hix, Partner / CFO at Amplēo, the fractional finance team on The Caviar Co account. Booked a 30-minute call the same afternoon. Engagement began the following week.
Direct intro.
Accounting-firm intro; a channel for both of us.
EDI partner intro — a two-way source of work.
Direct founder intro.
The first one, two weeks after the agreement was signed.
A dedicated outbound sequence written from Scott's own service overview and sent to 85 sellers in the SKU.io pipeline, positioning Scharf Consulting for the operational work that has to happen before software can help. Built directly from the sample introduction Scott supplied on 2024-10-29.
Built for you, kept here so you are never hunting through Slack for a link. Need something else compiled — an account history, a comparison, a feature answer for a selection engagement? Ask in Slack and it will show up in this list.
Every Freshdesk ticket and Slack thread on The Caviar Co account, compiled into a single timeline: what broke, what we fixed, what stayed open, and where the operational gaps sit. Built for the Scharf Consulting engagement.
Written in response to your B2B questions on the Rouge account. Covers price lists, customer-specific pricing, quotes, order approval and the wholesale order flow — the material you can hand to a seller mid-selection.
Head-to-head on the B2B feature set, built for selection work. Use it as a source when you are assembling a comparison matrix.
Open-source skills that let terminal-based AI agents like Claude Code operate SKU.io through the API — pull inventory, reconcile, build purchase orders, run a close checklist. Relevant to any client of yours who is still doing that work by hand in a spreadsheet.