HR Policy Packages for E-commerce software providers
What this looks like in your business
For an e-commerce software provider, a policy package is the written answer to questions that arrive in the middle of a sale week. Who is expected to be reachable, what a night on standby earns, who may open a merchant's store and when, whether a developer may build a paid app on the side. Engineers, onboarding specialists and support agents each meet different questions, and the founder's replies in chat do not always match. GullyHR drafts the set, Starter, Core or Complete, in one structure with an employee FAQ, a workflow and forms. Your own legal adviser reviews each draft before it is issued, and you choose which policies apply.
Which questions cause disputes in a platform business
Policy gaps here show up as arguments between people who like each other. Standby is the first. If the rule on who is paged, how long a response may take and what time off follows a night call lives in a manager's head, the engineers who always say yes carry the load and resent it. Access to merchant stores is the second. Support agents and onboarding specialists see merchant data, orders and customer lists, so a missing rule on viewing, copying or discussing them is a risk to your merchants' trust as well as to your own. Leave around sale days is the third, because a request that is fine in March is a problem in the week of a promotion. Outside work is the fourth: theme, plug-in and app developers are asked whether they may build for the same platforms in their own time. Remote work across time zones, conduct with partner agencies and how a support-versus-engineering complaint is raised complete the list. Each of these needs a written rule that managers apply the same way.
How GullyHR chooses and shapes the policies
GullyHR starts with an inventory of what you have, which for most platform companies is an offer letter template, a few chat messages and a paragraph in a wiki. It then reads those against your real teams: engineers on standby, onboarding specialists working with new merchants, agents across shifts, partner managers dealing with agencies. Starter settles the handful of policies that cause the most trouble. Core adds the next group, and for a platform company that would include standby and cover, merchant data and system access, and leave around peaks. Complete covers the whole set in three stages. Every policy follows one structure: purpose, who it applies to, the rule, the workflow, the forms and an employee FAQ written in plain words. Management choices are settled before drafting, so a draft does not hide a decision. For example, the founder decides whether a sale-week leave limit is firm. Definitions are kept the same across documents so that standby, working day and merchant data mean one thing everywhere. The employee FAQ is written last, once the rule is settled, in the questions a support agent or engineer would really ask.
Choosing between Starter and Core
Suppose a hosted storefront provider has a growing platform team and a support floor, and its founder, Priya, is deciding between Starter and Core. GullyHR lays her current documents beside the sale calendar. The offer letter mentions standby but gives no rule. The wiki says merchant data is confidential but not who may view a store or for how long. Leave is approved by whoever is asked first. Priya notices that one engineer was told by one manager that standby nights earn time off and by another that they do not. The advice is Core, because the standby, merchant data and leave policies are the ones that cause disputes and exposure, and Starter would leave one of those three out. Priya agrees. During drafting GullyHR finds that the leave document defines a working day differently from the standby document, and settles one definition with her before either is written. The drafts then go to Priya's legal adviser for review. Priya, not GullyHR, decides what each rule says, and the policies not chosen now stay on a list for the next review.
Owners, forms and what stays with you
A policy only works if a named person applies it and a record shows it was. Settle an owner for each: the head of engineering for standby and access, the head of support for shift and leave cover, and an operations lead or the founder for conduct and complaints. Settle which forms go with each policy, such as a standby swap form, an access request and removal form, and a leave request that shows the sale-day calendar. Settle where signed acknowledgements are kept and how new joiners receive the set on day one. Agree when each policy is reviewed, since a platform company's practices change as products do. What stays with you is every choice the policy records: how much notice a sale-week leave limit needs, what the standby rule gives, what outside work you will allow. The drafts go to your own legal adviser before issue, and GullyHR does not give a legal opinion on any clause. A package can grow as you do, by adding the next group when the team does, such as when a second support shift or a partner programme begins.