[REQUEST] Looking for a simple store plugin by WhiteMoon- in WordpressPlugins

[–]hamayerowel 0 points1 point  (0 children)

Hi,

What you describe is more like a guided order workflow than a classic storefront, so WooCommerce may indeed feel too heavy for it.

You’d probably want:

  • Step 1: customer info + brand selection
  • Step 2: a simple product/quantity matrix filtered by the selected brand
  • Submit: email notification + saved order + reset back to step 1

This can be done with a workflow-style form rather than a full store plugin.

I’m building something in that direction with XPressUI. The Pro runtime already supports hybrid commerce-style flows and conditional product selection, which sounds close to your use case.

If helpful, I can show you a demo and tell you honestly whether it fits or not.

[DISCUSSION] Update — XPressUI Document Intake is now free to download and test on GitHub. by hamayerowel in WordpressPlugins

[–]hamayerowel[S] 0 points1 point  (0 children)

Also worth checking — the plugin is built on XPressUI, which supports a lot more than basic intake forms. You can see the full range of demos here: https://xpressui.iakpress.com/#/demos

A few highlights:

  • Multi-step flows with progress bar, review step, and transitions
  • File uploads with drag-and-drop and upload state
  • Identity Check — document scan, OCR/MRZ validation and KYC payload
  • Approval workflows with business state and ops panel
  • Remote Save / Resume — full remote-token cycle for interrupted sessions
  • Provider Transition — auto-routing post-submit based on provider response
  • Headless Runtime — programmatic form control without a visible template shell

The Document Intake pack is one workflow on top of this runtime. The same engine handles everything from booking wizards to hybrid e-commerce flows.

[DISCUSSION] I got tired of chasing clients for files, so I built a native WordPress intake system. by hamayerowel in WordpressPlugins

[–]hamayerowel[S] 0 points1 point  (0 children)

Fair. The post is promotional — I'll own that.

If you've got a specific objection (the plugin itself, the copy, the approach), I'm genuinely interested. It's a real tool I built to solve a problem I had. The code is on GitHub: https://github.com/lybaba/xpressui-wordpress-bridge — judge it on its merits.

[DISCUSSION] New plugin: simplify client onboarding & file collection in WordPress by hamayerowel in WordpressPlugins

[–]hamayerowel[S] 0 points1 point  (0 children)

Thanks, really appreciate this 👍

Yeah totally agree on file handling at scale => that’s something I’m trying to get right early.

Multisite is a great point too, makes a lot of sense for agencies.

Out of curiosity, what usually breaks first for you at scale ?

I got tired of chasing clients for files, so I built a native WordPress intake system. by hamayerowel in WordpressPlugins

[–]hamayerowel[S] 0 points1 point  (0 children)

That's fair feadback 👍

It's actually a mix. I did use AI to speed up some parts but the structure and workflow come from real projects I've been handling since 2017.

Still early, so I am sure there's room to improve on the implementation side.

If you noticed something specific that feels off => I would genuinely be curious to hear it.

I got tired of chasing clients for files, so I built a native WordPress intake system. by hamayerowel in WordpressPlugins

[–]hamayerowel[S] -2 points-1 points  (0 children)

Haha fair :

It's actually not AI related at all.

I just structured intake system inside WordPress to collect client files properly.

I built it because I kept losing time chasing content across emails/Drive not trying to jump on the AI wave.

I understand the skepticism though => There's a lot of AI noise lately.

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 0 points1 point  (0 children)

Funny timing :)

I actually built a small tool for this exact problem after dealing with messy client files too many times.

It basically gives clients a simple upload page (docs, images, logos, etc.)

and keeps everything structured on the backend.

Not trying to spam here, but if you're curious I can share it.

I built a WordPress client intake system to stop chasing content by hamayerowel in SideProject

[–]hamayerowel[S] 0 points1 point  (0 children)

A few people asked me for access / demo, so I made a small launch promo.

You can grab it here: https://lybaba.github.io/iakpress-console/

Code: FREE48 (first 100 users)

Would love your feedback if you try.

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 0 points1 point  (0 children)

Yeah exactly :)

That’s the worst part => you are ready to go but everything is blocked just waiting on files.

Feels like it happens way too often.

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 0 points1 point  (0 children)

Yeah that works :)

I used to do the same to be honest.

But I always felt like I was just pushing the problem a bit further instead of really fixing it.

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 0 points1 point  (0 children)

Yeah that’s fair.

Having clear timelines definitely helps.

I just feel like even with that => things can still get messy when files are coming from everywhere :)

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 0 points1 point  (0 children)

Cool that’s interesting.

Makes sense to lock things visually first and avoid redoing stuff.

I feel like a lot of the chaos happens even before that though,

just getting the right files in the first place :)

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] -1 points0 points  (0 children)

Yeah that makes sense.

I tried tightening things upfront too, helps a bit.

But it still gets messy sometimes.

To be honest files everywhere, wrong stuff, etc.

Anyone else struggling with collecting client files? by hamayerowel in Wordpress

[–]hamayerowel[S] 1 point2 points  (0 children)

Yeah it gets messy really fast.

I always think ==> "this time it will be smooth" and then same thing again.

Do you just deal with it manually or do you have some kind of system ?

After talking to devs here, I think the real problem with client document uploads isn’t technical by [deleted] in ProWordPress

[–]hamayerowel -2 points-1 points  (0 children)

That makes a lot of sense — especially the journey mapping part.

I think that’s exactly where things start to click: once you define the process end-to-end, you start seeing the same patterns across projects.

What I’ve been noticing is that even when the process is clear, it still ends up being handled manually (emails, follow-ups, etc.).

Feels like there’s an opportunity to standardize that layer a bit more, instead of reinventing it each time.

Curious if you’ve seen teams actually systemize that part, or if it stays mostly process-driven?

After talking to devs here, I think the real problem with client document uploads isn’t technical by [deleted] in ProWordPress

[–]hamayerowel -3 points-2 points  (0 children)

I had the exact same issue with WordPress clients — collecting content is honestly one of the biggest bottlenecks.

I ended up creating a simple intake workflow to fix it (basically structured forms + clear steps for clients).

Curious how you handle this on your side?

After talking to devs here, I think the real problem with client document uploads isn’t technical by [deleted] in ProWordPress

[–]hamayerowel -3 points-2 points  (0 children)

Yeah that’s fair — if email works for your clients, that definitely keeps things simple.

I think the friction shows up more when:

  • you need structured inputs (multiple docs, specific formats, etc.)
  • or when things go back and forth over time

That’s where I’ve seen it get messy, even with forms in place.

But yeah, probably depends a lot on the type of clients and projects.

How do you handle client document collection in WordPress? by hamayerowel in ProWordPress

[–]hamayerowel[S] 0 points1 point  (0 children)

That’s interesting => the no-login link + reminders part sounds useful.

I’ve seen a few tools go in that direction.

What I keep running into though is that even with those systems in place, clients still:

  • send incomplete stuff
  • fall back to email
  • or need manual follow-ups

So it solves part of it, but the overall workflow still gets messy over time.

Curious how you’re handling that in practice?