Hey @ogasawarakyohei thanks for clarifying here. You’re right, we do technically limit shops to one cart transform function per shop, however, my understanding is that there is a bit of an exception if you install multiple custom apps, each of those can register its own Cart Transform Function, so technically you can exceed the “one function” limit for a single store, but only if you’re creating custom apps (There’s a bit more info in the community thread here).
A couple of things to keep in mind though!
Using multiple custom apps can bypass the one-function limit, but each app demands its own OAuth flow, hosting, and permissions, and there’s no guarantee on the execution order of their functions, so results can be unpredictable (which is why we don’t usually recommend this). Our policy also does discourage splitting a single product into multiple single-purpose apps if you ever go public, so I did just want to mention that.
That said, I totally understand the need for native time based support. Just want to make sure I’m understanding this correctly here though. Would you be needing sub-functions to be running at once, and could you share roughly how many separate sub-functions you’d need running/whether their execution order must be deterministic? I’m also curious if a built-in “auto-add target product” feature inside Discount Functions would cover most of your use-case.
I can’t guarantee that this would be rolled out or when, but. I’m happy to do some more digging into this for you internally here just to make sure I’m understanding things correctly and I can keep this thread updated as soon as I have more concrete timelines.
Thanks again for all the context here, really appreciate it and hope to hear back from you soon